Remove JIRA_SCHEMA_ID from entire application

- Remove JIRA_SCHEMA_ID from all documentation, config files, and scripts
- Update generate-schema.ts to always auto-discover schemas dynamically
- Runtime application already discovers schemas via /objectschema/list API
- Build script now automatically selects schema with most objects
- Remove JIRA_SCHEMA_ID from docker-compose.yml, Azure setup scripts, and all docs
- Application is now fully schema-agnostic and discovers schemas automatically

docs/AZURE-RESOURCES-OVERVIEW.md

@@ -78,7 +78,6 @@ These secrets should be stored in Azure Key Vault:
 | `SessionSecret` | Session encryption secret | `a1b2c3d4e5f6...` (32+ chars) |
 | `JiraOAuthClientId` | Jira OAuth Client ID | `OAuthClientId123` |
 | `JiraOAuthClientSecret` | Jira OAuth Client Secret | `OAuthSecret456` |
-| `JiraSchemaId` | Jira Assets Schema ID | `schema-123` |
 | `DatabasePassword` | PostgreSQL admin password | `SecurePassword123!` |
 
 ---
@@ -171,7 +170,6 @@ az webapp log tail --name cmdb-frontend-prod --resource-group rg-cmdb-insight-pr
 - `JIRA_OAUTH_CLIENT_ID` (from Key Vault)
 - `JIRA_OAUTH_CLIENT_SECRET` (from Key Vault)
 - `JIRA_OAUTH_CALLBACK_URL`
-- `JIRA_SCHEMA_ID` (from Key Vault)
 - `SESSION_SECRET` (from Key Vault)
 - `FRONTEND_URL`
 - `APPINSIGHTS_INSTRUMENTATIONKEY`