feature[REMOVED][devtools]: turn off / hide location based component filters

[hoxyq]

Following #28265, this should disable location-based component filters.

// Following __debugSource removal from Fiber, the new approach for finding the source location
// of a component, represented by the Fiber, is based on lazily generating and parsing component stack frames
// To find the original location, React DevTools will perform symbolication, source maps are required for that.
// In order to start filtering Fibers, we need to find location for all of them, which can't be done lazily.
// Eager symbolication can become quite expensive for large applications.

I am planning to publish a patch version of RDT soon, so I think its better to remove this feature, instead of shipping it in a broken state.

The reason for filtering out these filters is a potential cases, where we load filters from the backend (like in RN, where we storing some settings on device), or these filters can be stored in user land (window.__REACT_DEVTOOLS_COMPONENT_FILTERS__).

Explicitly tested the case when:

1. Load current RDT extension, add location-based component filter
2. Reload the page and observe that previously created component filter is preserved
3. Re-load RDT extension with these changes, observe there is no previously created component filter and user can't create a new location-based filter
4. Reload RDT extension without these changes, no location-based filters saved, user can create location-based filters

[huntie]

LGTM 👍🏻 One thing is I would prefix the commit as "feature", if using a scoped commit msg format.