[TypeSpec] Create Liftr - Elastic Azure Integration specification for SDK generation

[Copilot]

This PR creates a complete TypeSpec specification for the Liftr - Elastic Azure Integration SaaS offer on Marketplace, enabling SDK generation for Go, Java, JavaScript, and Python.

Overview

The Liftr - Elastic Azure Integration service provides monitoring and observability capabilities through Elastic's search and analytics platform, integrated seamlessly with Azure services. This implementation follows the established Liftr service patterns used by other marketplace integrations.

Changes Made

TypeSpec Specification

• Created complete TypeSpec specification at specification/liftrelastic/Elastic.Azure.Management/
• Namespace: Elastic with API version 2025-06-30-preview
• Resource Model: OrganizationResource following Azure Resource Manager patterns
• Operations: Full CRUD operations (GET, PUT, PATCH, DELETE, LIST)

Key Features

• Elastic Monitoring Properties: Configuration for Elastic stack version, endpoints, and deployment settings
• Deployment Configuration: Supports multiple deployment sizes (Small, Medium, Large, ExtraLarge) with configurable data retention
• Single Sign-On Integration: Enterprise SSO capabilities through Azure AD
• Marketplace Integration: Full Azure Marketplace billing and subscription management via LiftrBase

SDK Configuration

Configured SDK generation for all required languages:

• Go: github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/elasticazure/armelasticazure
• Java: com.azure.resourcemanager.elasticazure
• JavaScript: @azure/arm-elasticazure
• Python: azure-mgmt-elasticazure

Files Created

• main.tsp - Core TypeSpec specification with resource definitions
• client.tsp - Client-specific customizations for all SDK languages
• tspconfig.yaml - SDK generation configuration
• cspell.yaml - Spell checking configuration
• README.md - Complete documentation
• Example files demonstrating API usage
• Generated OpenAPI specification

Validation

• ✅ TypeSpec compiles successfully without errors
• ✅ Passes all Azure Resource Manager validation rules
• ✅ Follows established Liftr service patterns
• ✅ Configured for beta release as specified in release plan 501

Release Plan Integration

Updated release plan work item 28197 with SDK package details for all languages. The specification is now ready for official SDK generation through Azure SDK pipelines.

Fixes #36247.

---

💡 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.

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ This PR is labelled with ArcReview. For this PR to be merged, it must pass an ARC review and be labelled ArcSignedOff.
  Email the ARC board to request review per this Contact section.
• ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide. In addition, refer to step 4 in the PR workflow diagram

[openapi-pipeline-app]

PR validation pipeline started successfully. If there is ApiView generated, it will be updated in this comment.