Catch tooltip v2 errors in older browsers

[alondahari]

• related to https://github.com/github/issues/issues/12468

Add try..catch to the functions to open and close the tooltip v2 to avoid flooding sentry with errors. This is a short term solution until the Primer team can get to the bottom of why this is happening even though we have a polyfill in place.

Rollout strategy

• Patch release
• Minor release
• Major release; if selected, include a written rollout or migration plan
• None; if selected, include a brief description as to why

Testing & Reviewing

Try to use a tooltip v2 with an older browser that doesn't support the tooltip api and check for any js errors. We haven't been able to reliably introduce the error, but we're seeing it happen in production.

Merge checklist

• Added/updated tests
• Added/updated documentation
• Added/updated previews (Storybook)
• Changes are SSR compatible
• Tested in Chrome
• Tested in Firefox
• Tested in Safari
• Tested in Edge
• (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

[changeset-bot]

🦋 Changeset detected

Latest commit: 39843b5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@primer/react	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

👋 Hi, this pull request contains changes to the source code that github/github depends on. If you are GitHub staff, we recommend testing these changes with github/github using the integration workflow. Thanks!

[github-actions]

size-limit report 📦

Path	Size
packages/react/dist/browser.esm.js	97.19 KB (+0.07% 🔺)
packages/react/dist/browser.umd.js	97.5 KB (-0.01% 🔽)