Filter markers for the web developer use case

We should implement a filtering for markers that would be suitable for web developers.

Currently in the active tab view, we keep only markers that have an innerWindowID, but all these markers aren't always suitable for a web developer.

Therefore we need either an allow list to filter markers further, or add a new "relevant for js" property in the schema that would make it more generic.

I'm filing this with the "active tab" label but I believe we could expose this filtering also in the full view, and independently of the "javascript" implementation toggle.

Example profile: https://share.firefox.dev/3uuQzOW

┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-516)