Un-breaking of building trunk

[jng]

Currently building MG trunk is broken due to upstream breaking changes from the CS-Map library. Due to my current focus on getting 4.0 out the door, the trunk has been left in a state of dis-repair for quite some time. Most of the "dev" work has been done on the 4.0 branch.

Once 4.0 hits the RC stage and we have made a FDO 4.2 branch, efforts should be made to get trunk buildable again.

An initial checklist:

• FDO trunk
  • Merge in remainder of changes from adsk branch
    • SQL Server Provider: Using new ODBC driver
    • FDO Core: API changes around FdoDateTime and vertical CS support in spatial contexts
    • SQLite Provider: Fresh rebase on top of their code
      • However, we must be cognizant of ​https://trac.osgeo.org/fdo/ticket/895 not happening again as this is what caused us to abort all of our code merge efforts for this provider. If this still happens, we cannot proceed.
• MG trunk
  • Merge in everything from 4.0 branch (once at final/RC)
    • In the event of conflicts, the 4.0 branch is the winner in all cases.
  • Fix up broken usages of CS-Map API
  • Merge in changes from adsk branch that we previously held off on
    • MgDateTime offset support
    • Vertical CS support in spatial contexts
    • New Layer Definition schema changes and stylization engine support for said changes