feat(react-component-annotate): Allow skipping annotations on specified components

[0Calories]

Some third party libraries involve components that have compatibility issues with the react-component-annotate plugin, and results in errors when the data-sentry properties are added as props. This PR introduces a bit of a bandaid fix by introducing an option to allow users to configure the names of components that should not have any annotations applied.

When using the standalone Babel plugin, you can configure this option like so:

// babel.config.js

{
  // ... other config above ...

  plugins: [
    // Put this plugin before any other plugins you have that transform JSX code
    // The options are set by providing an object as the second element in the array, but not required
    ['@sentry/babel-plugin-component-annotate', {ignoreComponents: ['Foo', 'Bar']}]
  ],
}

When using the Sentry bundler plugins, you can configure this option like so:

sentryVitePlugin({
    // ... other options
    reactComponentAnnotation: {enabled: true, ignoreComponents: ['Foo', 'Bar']},
}),

TODO: Add tests and allow providing a source file location, since it is possible for multiple components to have the same name, but you may not want to skip annotation on all of these.

[lforst]

@0Calories can we expedite this PR?

[0Calories]

@lforst I'll try to finish it on friday, I believe it just needs tests

Also:

allow providing a source file location, since it is possible for multiple components to have the same name, but you may not want to skip annotation on all of these.

This unfortunately will have to be done in a followup PR. For now, I want to at least expose the option to skip specific components by names as that will at least provide an option for users who are struggling with incompatible components

[nathan-gage]

will it be possible to resolve #611 with this PR -- i.e., not trying to name <React.Fragment/>s used in headless?