Rename `InboundFilters` integration to `EventFilters`

[Lms24]

Description

If we get a chance to change this, I propose to rename the inboundFiltersIntegration because its name doesn't make a lot of sense. Open for other suggestions but logically, outboundFiltersIntegration makes way more sense.

After a bit of reflection, I think outboundFilters only makes sense if you knew the previous name, so I propose something like EventFilters for a fresh perspective :)

Reasons why I think "InboundFilters" is a confusing name:

• Nothing is "inbound" in the SDK world in the sense that we would filter incoming events. On the contrary, this integration filters out outbound events the SDK would send to Sentry.
• We have a product feature called "Inbound Filters" which users sometimes confuse or mix up with the SDK integration.
• The integration name does not reflect the purpose well. Granted, eventFilters isn't perfect either but at least it suggests that events (errors and transactions) get filtered out by this integration.

This integration is likely used a lot so we should probably leave it deprecated for a major or two before we actually remove it.

Steps:

• feat(core): Rename inboundFiltersIntegration to eventFiltersIntegration #15434
• Remove in adequate major (TBD if v10 or later)

[Lms24]

Renaming was done via #15434, including the deprecation of inboundFiltersIntegration.

Leaving this issue open and in the v10 milestone to remove the export with the old name.