Modify creation scripts to avoid version-specific or installation specific clauses

[rushj4]

Current database creation scripts include some options that may make it difficult to run or evaluate changes.

For example, table creation scripts contain the clause "OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF"; this is only valid for SQL 2019 and above, and will cause the table create to fail if run on SQL 2017 or earlier. Since Off is the default setting, removing the clause should have no effect on SQL 2019 and above systems.

Also, we find data compression settings on many tables and indexes. These would seem to be installation specific, and when included may generate false change reports when comparing Current CEDS to our installation. Similarly, please ensure all keys, constraints, and defaults are named; we want to avoid generated names showing as differences.