Use current axis only for calculating bottleneck areas This is a fixup of rev. cf25b23e3eec, which introduced historic data for the waterway axis but missed to take this into account in the calculation of bottleneck areas, leading to sometimes excessive runtime and bad results due to multiple (almost) equal axis geometries being considered as candidates in the bottleneck stretch. The database migration tries to recalculate all bottleneck areas, while some might fail that did not fail on import. A warning message is emitted for these and the area is left untouched.

# documentation
**/README*
**/docs
**/*.md

# backend binary
cmd/gemma/gemma

# Dependency directories
.buildbase
**/node_modules

# local dotenv environment variables file
client/.env.local

# Tags tables
**/TAGS