Added path normalization service with tower-http

[ezrasingh]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

The PR updates the path normalization to allow for either a trailing slash or no trailing slash in client requests. This ensures consistent URL handling regardless of the presence of a trailing slash.

Key Changes

• Added support for path normalization using towerhttp.
• Implemented a middleware for normalizing paths to ensure consistent URL handling.

Related Tickets & Documents

• Related Issue Add Path Normalization For API Endpoints #4
• Closes Add Path Normalization For API Endpoints #4

QA Instructions, Screenshots, Recordings

• To test the changes, run the server and make requests to the endpoints GET /api/v1/geohash/xn6mfn and GET /api/v1/geohash/xn6mfn/. Both should return the expected results, regardless of the trailing slash.

Added/updated tests?

• Yes
• No, and this is why: I believe this change is better suited for end-to-end testing rather than unit tests.
• I need help with writing tests