feat: Add UDT for all avm/res/sql/server submodules

[peterbud]

Description

This PR adds the remaining UDTs for al SQL submodules

Pipeline Reference

Pipeline

Pls note that WAF fails due to missing maintenance window in my subscription.

Type of Change

• Update to CI Environment or utilities (Non-module affecting changes)
• Azure Verified Module updates:
  • Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:
    • Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
    • The bug was found by the module author, and no one has opened an issue to report it yet.
  • Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
  • Breaking changes and I have bumped the MAJOR version in version.json.
  • Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• I have run Set-AVMModule locally to generate the supporting module files.
• My corresponding pipelines / checks run clean and green without any errors or warnings

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[microsoft-github-policy-service]

Important

If this is a module-related PR, being submitted by the sole owner of the module, the AVM core team must review and approve it (as module owners can't approve their own PRs).

To indicate this PR needs the core team''s attention, apply the "Needs: Core Team 🧞" label!

The core team will only review and approve PRs that have this label applied!

[AlexanderSehr]

As a recommendation as per the other type imports from the avm-common-types, please move this import on top of the parameter where it is used. Makes it a bit easier to understand where the type is coming from.
The reamining types are fine were they are. Would just be nice to have the consistency for the common types.

[peterbud]

It is not used at a parameter, but as a type within the databasePropertyType. You cannot move a type import inside a type declaration AFAIK. What would be your suggestion for that?