Fix workload profile setting

[alefteris]

Description

Setting a workload profile wasn't working, because the check for consumption profile to set workload_profiles_consumption_enabled didn't account for the fact that the workload_profile variable includes also the max/min count with default values. So I fixed this part. Also fixed is the part that sets the workloadProfiles for the azapi resource to use the correct format.

The rest of the changes are white-space changes from running the avm pre-commit and adding the modtm provider that was needed for the module to work, because of previous commits in main the branch.

avm pr-check fails because some more changes are needed, I think because of updates to interface specs.

Type of Change

• [ ] Non-module change (e.g. CI/CD, documentation, etc.)
• [x] Azure Verified Module updates:
  • [x] Bugfix containing backwards compatible bug fixes
  • [ ] 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.
  • [ ] Breaking changes.
  • [x] Update to documentation

Checklist

• [x] I'm sure there are no other open Pull Requests for the same update/change
• [ ] My corresponding pipelines / checks run clean and green without any errors or warnings
• [x] I did run all pre-commit checks

[microsoft-github-policy-service[bot]]

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the TF Issue Triage documentation.

[kewalaka]

@alefteris this looks good but i'm going to close in favour of the azure/wp-fix branch where i've added linting fixes