[Improvement]: Migrate JS Library Icons to Use Internal CDN Instead of Third-Party URLs

Is there an existing issue for this?

• I have searched the existing issues

Summary

Within the JS Library feature of our application, we currently rely on third-party URLs to source icons for various JavaScript libraries. This dependency on external resources can lead to issues such as broken icons and inconsistent user experiences if those URLs become unavailable.

Proposed Solution:

Migrate all JS Library icons to be hosted on our internal CDN to ensure their consistent availability and performance. Update the icon fields in the JS Library configurations to point to the new CDN-hosted versions.

Benefits:

Ensures that icons for JS libraries are always available and not dependent on external services. Potentially faster icon loading times by reducing reliance on third-party hosts. Enhanced security and greater control over the assets used in our application.

Why should this be worked on?

This should be worked on to ensure reliability, performance, and security. By moving JS Library icons to our internal CDN, we eliminate the risk of broken icons from third-party outages, reduce load times, and maintain better control over our resources. This leads to a more consistent and dependable user experience.