Update integration format for better handling of multiple asset types

[Swiddis]

Description

To support multiple installation paths for integrations better, part of that is refactoring the current install flow to make the different types of assets more uniform. This PR:

• Updates the integration type
• Updates frontend/backend usage of integration assets for new type
• Fixes several lints around the frontend in preparation for [FEATURE] Multiple installation flows for Integrations. #1462
• Adds a migration path for any installed dynamic integrations

Next steps are refactoring the installation flow to support multiple install paths, using these extensability updates.

Notice: I noticed while writing this that we don't have any unit/integration tests that ensure that all types of assets are being correctly installed. This will be included as part of the installation workflows PR, the current PR is already fairly big as-is. Followed the boy scout rule for some other misc. changes like removing dead code and fixing misused types.

Issues Resolved

Closes #1444

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

Attention: Patch coverage is 81.69014% with 13 lines in your changes are missing coverage. Please review.

Project coverage is 54.36%. Comparing base (290415a) to head (fc22b95).

Files	Patch %	Lines
...egrations/components/create_integration_helpers.ts	54.54%	5 Missing ⚠️
...grations/components/__tests__/testing_constants.ts	42.85%	4 Missing ⚠️
...ents/integrations/components/setup_integration.tsx	50.00%	2 Missing ⚠️
...tors/integrations/repository/integration_reader.ts	93.54%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1498      +/-   ##
==========================================
+ Coverage   54.26%   54.36%   +0.10%     
==========================================
  Files         343      344       +1     
  Lines       12338    12353      +15     
  Branches     3173     3173              
==========================================
+ Hits         6695     6716      +21     
+ Misses       5587     5581       -6     
  Partials       56       56              

Flag	Coverage Δ
dashboards-observability	54.36% <81.69%> (+0.10%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Swiddis]

This is the core change, most of the refactoring is following the consequences of this type update

[Swiddis]

Not 100% sure I've set up migration correctly, messed with it a bit to get the type checking to work out but I'm not sure when this migration triggers.

[YANG-DB]

Hi
How would migration be handled an by whom ?
For example if I have a migration script - where can I specify it ?

[Swiddis]

Migrations run on OSD startup, it's handled in OSD and will apply to all of the installed templates that are on a lower version. But I'm not sure how OSD detects the version.

For content, I migrated all of the prebuilt content, but I'll need to update the bundle script for the new version.