Migrate database schema to modern types and improve string handling

[stevewgr]

Description

This pull request migrates the database to address legacy data types and improve storage and processing efficiency. Specifically:

1. Migration from ntext/text to varchar:

   • These legacy types are deprecated in newer MSSQL versions and will be fully removed in future versions.
   • Updated the layout of K_NPCPOS to align with the official configuration and the loading order used by N3ME and server files.

2. Migration from CHAR to VARCHAR:

   • CHAR columns caused inconsistencies due to fixed length and padded whitespaces.
   • VARCHAR handles variable-length strings more efficiently, reducing IO overhead, optimizing storage, and improving performance.
   • This resolves misuse of CHAR and addresses inefficiencies in storage and operations.

Additional Notes

• This is the initial step in cleaning up inconsistencies in the database schema and migrating towards the use of MSSQL 2019's new collation: Latin1_General_100_CS_AS_SC_UTF8.
• The changes maintain compatibility with the current server files; no updates to the server are required.
• Previously, the server files (C++ codebase) had to call a Trim function to handle trailing spaces in strings retrieved from CHAR columns. With this migration to VARCHAR, such trimming may no longer be necessary but can remain in place without causing any issues. Cleanup of this logic can be done incrementally.

Why These Changes?

• Future-proofing: Preparing the database for MSSQL updates and removing reliance on deprecated types.
• Efficiency: Optimizing database operations by using appropriate data types.
• Consistency: Reducing discrepancies caused by padded strings and fixed-length columns.

Impact

• No breaking changes.
• Server files remain compatible without modification.
• Performance and consistency improvements in database operations.

Next Steps

Further cleanup tasks, such as updating server-side string handling logic (e.g., trimming), can be addressed incrementally without immediate urgency.

[stevewgr]

Note that if you can't load the big diff in your browser, you can add .patch at the end of the commit message and it will render it:
https://github.com/ko4life-net/ko-db/pull/37/commits/6e9f29ca06444159e58e63f35b59ac31f09f6b51.patch

You can also use a browser extension to colorized it.