feat: add versioned assets + fix HMR

[EmileRolley]

Before:

Now:

Tasks

• [x] Dynamically import versioned assets
• [x] Update the UI to be able to switch versions
• [x] Add the version in the URL
• [x] Dynamically import different versions of french-law
• [x] Bind a french-law version to its corresponding asset version
• [x] Automatically update assets when a new released is made for catala-web-assets or french-law
• [x] Investigate the differences between the latest version and the others: there is duplicated steps for the same children in the latest version (catala-explain bug?)
• [x] Big cleaning and component factorization
• [x] Update the README about the new assets sync mechanism
• [x] Publish and use the changes for catala-explain

[denismerigoux]

Am I correct to understand that now the main landing page is only 700kb and that you only load the 6 MB source code of the housing benefits when needed?

[denismerigoux]

As of now you hardcoded in this git repo the contents of each version of the dependent packages we use. Is there a way with npm/other JS packaging tools to use multiple versions of a single package so that we don't have to hardcode the contents of the versions of the packages?

[EmileRolley]

Am I correct to understand that now the main landing page is only 700kb and that you only load the 6 MB source code of the housing benefits when needed?

Yep :+1:

[EmileRolley]

As of now you hardcoded in this git repo the contents of each version of the dependent packages we use. Is there a way with npm/other JS packaging tools to use multiple versions of a single package so that we don't have to hardcode the contents of the versions of the packages?

I copied past to quickly test the dynamic import but I can look to see if it's possible yes!

[EmileRolley]

It seems possible with aliases but I wonder how far it can be automated :thinking:

[bzg]

Mh.. this looks like an issue where @garronej expertise could be of some help 🤞🏻