feat: Implement mfr truncation fix and enhance invoice handling

- Added a new SQL script to address the "String or binary data would be truncated" error in mfr sync by widening the Note fields in service objects and companies to NVARCHAR(MAX).
- Updated the table types and associated stored procedures to accommodate the changes, ensuring compatibility with existing data.
- Queued a re-sync for previously rejected rows due to truncation issues.
- Created application logins for fuchs_fds and fuchs_web with placeholder passwords for initial setup.
- Introduced functions for invoice backdating and invoice date retrieval to streamline invoice processing.
- Developed a password generation function with customizable parameters for length and character types.
- Added a random number generation function to support password creation.

Fuchs_Database/Security/Logins.sql

@@ -0,0 +1,12 @@
+-- Application logins (SQL authentication). They already exist on every environment and their real
+-- passwords live in Azure Key Vault; nothing here is a secret.
+--
+-- The file exists so the users in this folder (fuchs_fds, fuchs_web) bind to a login when the project is
+-- built: SSDT reports a user whose login is not in the model as error SQL71501, which is what kept the
+-- database project from building at all (ADR 0036). On an existing server the deployment sees the login
+-- as present and leaves it alone (SSDT never compares passwords); on a fresh server it is created with
+-- an expired placeholder that must be changed before the login can be used.
+CREATE LOGIN [fuchs_fds] WITH PASSWORD = N'Change-Me-Before-First-Use-1!' MUST_CHANGE, CHECK_EXPIRATION = ON, CHECK_POLICY = ON;
+GO
+CREATE LOGIN [fuchs_web] WITH PASSWORD = N'Change-Me-Before-First-Use-1!' MUST_CHANGE, CHECK_EXPIRATION = ON, CHECK_POLICY = ON;
+GO