Bug: Fix broken ui components when angular is disabled

[jackw]

What is this feature?

I'm not sure if we should apply the change in this PR or wait for individual tasks to remove bootstrap usage from components. e.g #76182 I could only find this one issue so not entirely sure how widespread bootstrap usage is. 🤔

This PR moves the bootstrap import from angular app to react app to resolve issues where certain components break due to missing bootstrap js when angular is disabled. We should consider this an interim solution to buy time for auditing / removing remaining bootstrap usage across the codebase without impacting users that have angular disabled in configs.

Why do we need this feature?

So angular can be disabled without causing ui issues.

Who is this feature for?

Grafana users

Which issue(s) does this PR fix?:

Fixes #76258

Special notes for your reviewer:

Please check that:

• It works as expected from a user's perspective.
• If this is a pre-GA feature, it is behind a feature toggle.
• The docs are updated, and if this is a notable improvement, it's added to our What's New doc.

[axelavargas]

Hey @jackw, thanks for fixing this issue 🥇 . I gave it a test locally, and it resolves the issue reported in these escalations (esc1 and esc 2 ).

My thoughts about this PR are aligned with yours. I think this should be an interim solution. Honestly, I don't know how many other components are relying on bootstrap js in our codebase, and without knowing that, we might be impacting more users who have Angular disabled in their configuration.

P.S. would like to hear your thoughts @dprokop and @torkelo

[dprokop]

@jackw - don't we want to backport this to 10.2.x?

@axelavargas - I don't know neither. Think we need to dedicate some time to learn more about this.

[grafana-delivery-bot]

Hello @jackw!
Backport pull requests need to be either:

• Pull requests which address bugs,
• Urgent fixes which need product approval, in order to get merged,
• Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

[jackw]

don't we want to backport this to 10.2.x?

Ah well spotted! I've updated the labels for backporting. 👍