Change the way SQL schema version changes are processed in LSMB 2.x

[neilt]

Right now we maintain a base SQL DDL file that corresponds to LSMB 1.4, then apply changes for each LSMB release since. Today, this results in a significant delay when creating a new company (database) as hundreds of DDL changes are applied.

With LSMB 2.0.0 the desire is to establish a new base SQL DDL file.

Design Criteria

What this means is that:

1. LSMB 2.0.0 will be a transition version
2. a new install of any LSMB 2.0.0 version will install a single LSMB 2.0.0 SQL DDL file and apply no changes
3. any upgrades from 1.x to 2.0.0 will use the old method of applying the long tail of changes since 1.4
4. any upgrades from 2.x to any newer version will apply the short tail of SQL changes since the LSMB 2.0.0 SQL DDL file

Impact

What this means is that any version prior to 2.0.0 must upgrade to 2.0.0 before upgrading to any 2.x.x version