## 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/test/test_event_definition.py
"""
    Creates an event, given an event dict. Currently just puts this data
    directly into clickhouse, but could be created via api to get better parity
    with real world, and could provide the abstraction over if we are using
    clickhouse or postgres as the primary backend
    """
    from posthog.models.event.util import create_event
    team = Team.objects.get(id=event.team_id)
    create_event(
        event_uuid=uuid4(),
        team=team,
        distinct_id=event.distinct_id,
        timestamp=event.timestamp,
        event=event.event,
        properties=event.properties,
    )
def create_event_definitions(event_definition: Dict, team_id: int) -> EventDefinition:
    """
    Create event definition for a team.
    """
    created_definition = EventDefinition.objects.create(name=event_definition["name"], team_id=team_id)
    return created_definition