ref(alerts): Don't pass "name" field

[ceorourke]

We have inconsistent data stored for issue alert rule data because we are sometimes saving the "name" field for filters, conditions, and actions and sometimes not. This is making it difficult to prevent creation of exact duplicate alerts (which I'm working on here) and makes queries more complicated since the data stored for the same thing has variance.

The first case where we store the "name" field is on FirstSeenEventCondition because it is hardcoded. Removing it does not affect the display on the alert details or edit page.

The second case is when you duplicate an alert. We do a GET request to the ProjectRuleDetailsEndpoint and the serializer adds the "name" fields so the front end can populate the data shown here:

and here:

We end up with data like:

[
    {
        'id': 'sentry.rules.conditions.first_seen_event.FirstSeenEventCondition',
    }, {
       'id': 'sentry.rules.filters.latest_release.LatestReleaseFilter'
    }
]

versus

[
    {
        'id': 'sentry.rules.conditions.first_seen_event.FirstSeenEventCondition', 
        'name': 'A new issue is created'
    }, {
        'id': 'sentry.rules.filters.latest_release.LatestReleaseFilter',
        'name': 'The event is from the latest release'
    }
]

stored in the database which makes it hard to query and compare. We should not send the "name" field to the backend when creating, duplicating, or updating an issue alert rule to avoid this.

We have a few places in the backend that are hardcoding this as well that I'll remove in a separate PR, and then I'll write a migration to remove it from any existing db rows so we have consistent data.