perf(devtools): scope Fast Refresh cache purges

[leno23]

Summary

This scopes the DevTools fastRefreshScheduled bridge event to the renderer that scheduled Fast Refresh.

Today the backend emits a global Fast Refresh event, so the frontend clears hook-name/AST metadata and refreshes the inspected element cache even when the selected element belongs to a different renderer. Passing the rendererID through the hook/agent/bridge lets the inspected element context skip the purge when it can tell the refresh came from another renderer.

Test Plan

• Not run locally yet; opening as draft for initial feedback.
• Intended checks before marking ready:
  • DevTools Flow/type checks
  • relevant React DevTools tests
  • manual multi-renderer DevTools smoke test if available

Risk / Notes

This preserves the existing behavior when rendererID is null or when no selected element is available. The optimization only skips the purge when the currently inspected element has a different rendererID than the renderer that scheduled Fast Refresh.

[meta-cla]

Hi @leno23!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!