Move 'constraints' markers to primitive and fix incompatibility with deploy

[mamcx]

Description of Changes

Refactor the definition of constraints into the primitives crate, removing duplications of logic and fix bug when

#[spacetimedb(table)]
struct Foo {
    #[primarykey]
    id: u32,
    #[unique]
    #[autoinc]
    other: u32
}

gives error Multiple primary columns defined for table, which shows up in the deployment of spacetimedb.com

API and ABI breaking changes

This changes the bits stored in the st_constraints system table.

Expected complexity level and risk

1

[mamcx]

NOTE: Currently IDENTITY implies UNIQUE but that is wrong: https://en.wikipedia.org/wiki/Identity_column.

However, to change this need we review how others are using this.

[mamcx]

This is added to check it compiles.

[kulakowski]

This looks good. You might have to change an integration smoke test which reads specific log lines because another table will add a log line and through the numbers off by one.

[mamcx]

Note: AUTO_INC right now is semantically ambiguous. it clashes with the purpose of IDENTITY (and is possible to have many of it) which is the recommended one when asked for auto-generated numbers.

I think we should use instead SEQUENCE and deprecate the use of this tag.

[kulakowski]

The code change itself looks good to me. I want to make sure we discuss in chat how we are going agree on the semantics you bring up here, before approving. Thanks for the pointers to documentation about it, Mario.

[kulakowski]

This looks good. You might have to change an integration smoke test which reads specific log lines because another table will add a log line and through the numbers off by one.

[kim]

Thanks! <3 the docs

[cloutiertyler]

IMO these are all confused. We should just have attributes which are separate from constraints:

IMO these shouldn't even be on the same axis.

We have the following column attributes:

• auto_inc

We should have the following table attributes:

• primary_key e.g. (col_a, col_b)
• indexed e.g. (col_a, col_b)

We should have the following table constraints:

• unique e.g. (col_a, col_b)

These are all mutually exclusive and should not be combined into a single "kind"

Also constraints != attributes!

[mamcx]

This will be addressed in a separate PR, this one is to solve the immediate issue with deploy.