[feature request] improved asset bundle handling

[b881659b]

Impacted versions: v13+ probably older versions as well

Current behavior:

Could you please improve the handling of asset bundles. There are a number of issues with the current approach:

• They are found under /web/content which is shared with other items that may require authentication/authorization making proxy configurations difficult.
• There are several instances when Odoo needs to recreate these bundles but only does so (as far as I understand) at startup. The problems are similar to Displaying "TypeError: Cannot read property 'bind' of undefined" error. #55226, Odoo Client Error when Saving Notes #51733 as well as other reports and many forum contributions.
• Manually triggering the process may fail (Regenerate assets bundles can bork odoo #51077).

Expected behavior:

I am not sure to what degree changing the process would affect third-party and community apps but if bundling
is required at all (instead of relying on /*/static), it may be better to:

• regenerate bundles as a cron job unless specific triggers can be identified
• do not retire existing bundles, at least not immediately, loading an 'old' version should not result in 404 as happens following the regeneration documented in Regenerate assets bundles can bork odoo #51077
• ideally, reference a fixed path and either return the 'latest' bundle with ETag or 30x redirects to the latest version
• a fixed path that is well documented to work with proxies (or public caches in general) would be great as long as it is certain that these bundles never include confidential elements

Thank you for your consideration.