Consider hash as part of the path

[ahocevar]

The tracker script already sends paths correctly with their hash part, but the database does not store them yet in url_path. So the UI cannot show them.

This pull request implements the missing piece of what was already described in #2960:

[vercel]

@ahocevar is attempting to deploy a commit to the umami-software Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

PR Summary

This PR adds support for hash-based routing by including URL hash fragments in the stored path, enabling proper analytics tracking for single-page applications that use hash-based navigation.

• Modified src/app/api/send/route.ts to concatenate currentUrl.hash with currentUrl.pathname when storing event paths
• Maintains compatibility with REMOVE_TRAILING_SLASH environment variable while adding hash support
• Completes implementation of hash-based routing tracking feature requested in issue feat: Add support for hash-based routing tracking #2960
• Enables accurate path analytics for SPAs using hash-based routing in the UI dashboard
• Aligns backend storage with existing tracker script behavior that already captures hash fragments

_{💡 (2/5) Greptile learns from your feedback when you react with 👍/👎!}

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}

[ahocevar]

Let me know if this should be turned on through an env variable (ADD_HASH_TO_PATH?), instead of always adding the hash to the path. However, I think the existing data-exclude-hash tracker script option should be sufficient.

[mikecao]

We are actually planning on adding a new column to the schema, url_hash, where we will store this data. That way users can decide to query the data if they want. The exclude hash setting will still apply.