As part of the initial work for RFC #32 we need to add a name and token_last_characters column to the ApiToken model.

This will help users more easily identify their API tokens and their intended use (see issue #9600 and https://github.com/getsentry/customer-feedback/issues/22).

I had a PR that accomplishes this on the backend (see #58876), but it needs to be broken up into three different ones in order to avoid any weird states and running multiple backfills.