fix: Inject component annotations into HTML elements rather than React components

[timfish]

• Closes reactComponentAnnotation. I use an unintended value for a prop. #492

Rather than inject attributes into React components which can cause incompatibilities with props, this PR changes the plugin to instead inject attributes into every HTML element in the component root.

Downsides

Potentially larger bundle sizes because the attributes will get injected into more elements.

[github-actions]

Semver Impact of This PR

🟢 Patch (bug fixes)

📋 Changelog Preview

This is how your changes will appear in the changelog.
Entries from this PR are highlighted with a left border (blockquote style).

---

Bug Fixes 🐛

• Inject component annotations into HTML elements rather than React components by timfish in #848

---

_{🤖 This preview updates automatically when you update the PR.}

[Lms24]

Thanks! I'll let other folks also review, especially also get perspective from ReactNative so that we're on the same page.

[Lms24]

super-l: Should we refactor the tests to use toMatchInlineSnapshot? Feels way easier to me to associate which test corresponds to which snapshot. Also fine to tackle as a follow-up or not at all if I'm missing a reason for keeping it as-is. WDYT?

[s1gr1d]

LGTM but as discussed offline, we can put this behind a flag to reduce bundle size impact

[antonis]

I think there are missing elements here (e.g. Pressable, TouchableOpacity that we are using in our samples). I'm not sure we can include everything in this list tbh. The users may also add custom components in their apps.
I was wondering if we can make this configurable so that we can add more elements on the RN SDK side or even allow for end users to extend.

[antonis]

As long as we do not pass experimentalInjectIntoHtml: true from the React Native SDK my understanding is that there is no change in behavior and the changes are safe to ship.
We can experiment with turning the feature ON and see the impact on our side. I think the main issue is the missing components before making this behavior default on the RN SDK.