The changeset macro should be a compiler annotation

[sgrif]

Documenting in case anyone wants to get involved. This is the last macro being invoked from our integration tests that needs to go away for 0.1 I intend for this to be #[can_update="users"]. This annotation should basically do what the macro does today, including all columns, but should specifically exclude the primary key of the table from the changeset.

As part of this, I think we should group all our non-derive annotations into a single namespace with each just being a key/value pair. e.g. #[yaqb(inserable_into("users"), can_update("users"))]. That change should affect #[column_name] as well. That can be a separate PR that pre-dates this change, part of this change, or just not done at all. It's not a 0.1 blocker.