Use .well-known path for assets to avoid conflicts

[reesericci]

Context

I was reading this blog post about assets and noticed that y'all were using /avo-assets. While it is extremely unlikely to conflict with anything, it is a possibility.

Proposition

To solve this, I think it would make sense to use a .well-known path, as defined in RFC 86150 which are designed for exactly this purpose: to define a pathname for well-known resources that won't conflict with the webmaster's path namespace. Additionally, these can be registered with IANA to further prevent conflicts.

[adrianthedev]

Sounds great! Are you open to send in a PR?

[reesericci]

Potentially, I just don't know the full extent of the usage of /avo-assets and I'm not super familiar with the codebase