fix: cycleway topic didn't ignore features that set value “no”

[joker234]

Description

The cycleway topic did include a lot of ways that are tagged with tag combinations like highway=residential and cycleway:both=no. This means it does not qualify as a cycleway. It just states that there isn't any cycle infrastructure. This PR proposes to change this behaviour and exclude all ways with just cycleway tags that equal to no.

To see the many ways this applies to and the extent of the error, one can have a look at this query. All shown ways are not covered by the fixed filter anymore (for Heidelberg): https://overpass-turbo.eu/s/2pma

Corresponding issue

None

New or changed dependencies

None

Checklist

• I have ensured my branch is mergeable with main (e.g. through git rebase main if necessary)
• My code follows the style guide and was checked with pre-commit before committing
• I have commented my code
• I have added sufficient unit and integration tests
• I have added new Hurl regression tests and checked all existing tests
• I have updated the CHANGELOG.md

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[SlowMo24]

this is definitely an improvement

But as long as roads are not treated as the two-way object they are, I still feel we have not approached the scientific optimum. I.e. if a road has a bike lane on both sides it should not be counted the same as one that only has it one one side IMO. Yet, I acknowledge that that is difficult to fulfil in this context.