Improve CI workflow

[rswrz]

Currently, a reusable workflow executes all jobs multiple times during various events in the PR lifecycle:

• PR created: All sub-workflows are executed.
• PR label added: All sub-workflows are re-executed (including tests).
• Code changes pushed to the PR: All sub-workflows are executed again.
• PR merged: Before the release, all tests are executed again, followed by the release process. This also applies if changes are pushed directly to the main branch.

This behavior is highly inefficient and negatively impacts performance. We need a more optimized solution to reduce redundant workflow executions.

Update Terraform module workflow usages and remove from project workflow

Preview Give feedback

1. terraform-azurerm-helloworld
2. terraform-module-template
3. terraform-azurerm-vm
4. terraform-azurerm-applicationgateway
5. terraform-azurerm-launchpad
6. terraform-azurerm-mssql-vm
7. terraform-azurerm-avd

[rswrz]

Idea from the last meeting (with @lixhunter and @rswrz):

• One workflow: Handles code-related tasks.
• Another workflow: Handles GitHub management tasks.

[rswrz]

Important

The automatic plan on pull requests should be refactored. We need to implement a quality gate before a plan (and apply) is actually executed to ensure that only validated changes are run.

[lixhunter]

prepared the workflow in #53

When it is merged we can move pull request an github release related workflows from module-ci to module-github.