Fix the distribution of resolvers on an uninitialised machine

[tadeas-hejnic]

Changelog Description

This pull request refactors how the addon metadata JSON file is handled to ensure it is always present and initialized correctly. The main improvement is the introduction of a utility function to centralize and simplify the creation and reading of this metadata file.

Testing notes:

1. start with blank setup (delete downloaded resolvers)
2. launch the DCC
3. test the resolver
4. test it also on a farm

[BigRoy]

LGTM

Only confusing thing is that function name ensure_addon_data_json you wouldn't really expect it to return a dict? Should it maybe just return {} and not make the file at all if it does not exist. Especially because ayon_usd_addon_first_init_utc does not seem to be used anywhere?

So maybe it should be get_addon_json_data?

[MustafaJafar]

I gave it a test locally on Houdini and Maya. It may take me a little longer to test it on farm.
I didn't look into the code or changes but from user perspective. it works as usual.

[tadeas-hejnic]

LGTM

Only confusing thing is that function name ensure_addon_data_json you wouldn't really expect it to return a dict? Should it maybe just return {} and not make the file at all if it does not exist. Especially because ayon_usd_addon_first_init_utc does not seem to be used anywhere?

So maybe it should be get_addon_json_data?

I have separated the ensure_addon_data_json to create_addon_data_json_file and get_addon_data_json, so now it has single responsibility and clear names.