GitLab

If we're going to make this many calls repeatedly, it better be
optimized.

When starting from scratch, if you go to the admin panel, set the first
API to display, and switch back to the APIs page, it's now out of date
with what's server-side.

Swagger UI doesn't offer any facilities to clean up after itself, so we
have to tolerate it.

This could be necessary in the future, so I want to lay the groundwork
now. Also, it's a potentially common need in development.

`git checkout` removes all the files already tracked by Git, but it
doesn't remove untracked files. That's what this change fixes.

This gets the tests passing again.

Also, make the handler strict mode.

Prevent exposing the existence of users from the login page

Revert a breaking change to user pools, retain them post-deletion

Instead of changing the schema, I'm enforcing it in the lambda, to avoid
Cognito's limitation of not being able to modify existing attributes
on user pools.

It's been broken for a while, so it's pretty useless to try to keep
around.

- display if users are admins in the registered table
- disable the promote button for existing admins
- indicate in the table which user you are
- disable the delete button if you're trying to delete yourself
- add BIG RED warning indicator to the modal if you're deleting an admin

Offer a workaround in case an API has a usage plan added after it's displayed

- also rename unused `cognitoUser` to `user`
- clarified some of the auth functions use and when they happen

Fix admin promotion to actually be idempotent