Update azure-resources module to follow style guide

[Copilot]

This PR updates the azure-resources module to comply with the project's style guide requirements, making minimal surgical changes to bring it into alignment.

Key Changes Made

AutoService Convention

• Added @AutoService annotations to all SPI provider classes (AzureVmResourceProvider, AzureFunctionsResourceProvider, AzureAppServiceResourceProvider, AzureResourceDetector)
• Removed manual META-INF/services files in favor of AutoService code generation
• Added AutoService dependencies to build.gradle.kts

Class Structure & Finality

• Made all resource provider classes final as they are public API classes
• Reordered class members to follow style guide convention: static fields (final before non-final), instance fields, constructors, methods, nested classes
• Made nested classes final where appropriate (e.g., Entry class, Builder class)

Build Configuration Fix

• Corrected build.gradle.kts which incorrectly contained GCP content instead of Azure-specific configuration
• Updated module name and description to properly reflect Azure resources

Code Organization

• Reorganized static field declarations to group related constants together
• Moved logger declarations to proper position in class organization
• Applied consistent ordering across all provider classes

Verification

• All existing tests continue to pass
• Code compiles without errors or warnings
• Spotless formatting checks pass
• AutoService correctly generates META-INF/services files in the JAR output
• Generated service files contain the expected provider classes

The changes maintain full backward compatibility while bringing the module into compliance with the established style guide conventions.

Fixes #133.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[trask]

@copilot why this change?

[Copilot]

This change makes the nested Builder class final to comply with the style guide requirement that classes should be marked final when they are not intended to be extended. The Builder class is an internal implementation detail that doesn't need to support inheritance.

[trask]

@copilot why add final here?

[Copilot]

Added final to comply with the style guide requirement that classes should be marked final when they are not intended to be extended. The Entry class is a simple data holder that doesn't need to support inheritance.