## Is your feature request related to a problem?

As a team accumulates data, they will have events/properties that are no longer in use that clutter their app.

Example from our team:
![image](https://user-images.githubusercontent.com/148820/143202334-42d73ab6-13be-4661-ba7a-83c86788b9e8.png)


## Describe the solution you'd like

Under event/properties stats allow 'hiding' events/properties from view.

## Describe alternatives you've considered

Alternatively, go the route of "verified" events/properties (as He@p) does - show those first. See also https://help.heap.io/category/heap-administration/data-governance/

## Additional context

Note: Existing reports, etc should still work well even with 'removed' events/properties.

Related: https://github.com/PostHog/posthog/issues/7126

#### *Thank you* for your feature request – we love each and every one!

posthog/api/property_definition.py
if type == "event":
            return dataclasses.replace(
                self, params={**self.params, "type": PropertyDefinition.Type.EVENT, "group_type_index": -1}
            )
        elif type == "person":
            return dataclasses.replace(
                self,
                should_join_event_property=False,
                params={**self.params, "type": PropertyDefinition.Type.PERSON, "group_type_index": -1},
            )
        elif type == "group":
            return dataclasses.replace(
                self,
                should_join_event_property=False,
                params={**self.params, "type": PropertyDefinition.Type.GROUP, "group_type_index": group_type_index},
            )
    def with_event_property_filter(