Allow Entire Config to be a URL

[danpastori]

Discussed in #505

^{Originally posted by danpastori May 4, 2022}

👉 Describe the problem

When initializing Amplitude, we have a huge config. With more audio files, it grows and grows. This can be un-sustainable when managing it within the context of a method parameter.

👥 Problem evidence & reach

Every user who manages a large config file

🥰 Describe the "impact" on users?

Users will be able to define their config from a URL which could lead to:

• Single source of truth management
• A file set up to handle just AmplitudeJS configs
• Dynamic audio within configs.

🏆 How to solve this problem

Allow the user to pass a URL that contains a config file as .json. This is the settings used to initialize AmplitudeJS.

💯 How do we validate the problem is solved?

Users can easily maintain AmplitudeJS configs through a separate file.