feat(azuredevops): add environment_pattern for extracting environment names from job/stage names (#8671)

This enhancement addresses the issue where the Azure DevOps plugin was unable to
correctly detect production deployments when the environment name is embedded in
job/stage names rather than being in a standard format.

Changes:
- Add `environment_pattern` scope config field that supports regex capture groups
  to extract environment names from job/stage names
- Collect both Job and Stage records from the timeline API (previously only Job)
- Add `identifier`, `type`, and `parent_id` fields to the Job model
- Update environment detection logic:
  - If environment_pattern is configured, extract the environment name first
  - Apply production_pattern to the extracted environment name
  - Fall back to matching production_pattern against job name if no extraction
- Fix default environment behavior: only default to PRODUCTION when
  production_pattern is not configured (was defaulting PRODUCTION always)
- Add comprehensive tests for the new functionality

Example configuration for pipelines with jobs like 'deploy_xxxx-prod_helm':
- deployment_pattern: deploy
- production_pattern: prod
- environment_pattern: (?:deploy|predeploy)[_-](.+?)(?:[_-](?:helm|terraform))?$

This extracts 'xxxx-prod' from the job name and then applies production_pattern
to correctly identify it as a production deployment.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>