feat(MonitoringAspect): add Fargate service support

[costmatt-amzn]

What

Wires Fargate services into the auto-applied MonitoringAspect so that teams relying on the aspect for fleet-wide auto-monitoring get Fargate coverage without manual opt-in.

Covers three cases:

Matched construct	Facade method	Metrics covered
ecs.FargateService (bare)	monitorSimpleFargateService	Service: CPU, memory, running/desired tasks
ApplicationLoadBalancedFargateService / NetworkLoadBalancedFargateService	monitorFargateService	Service + ALB/NLB + target group
QueueProcessingFargateService	monitorQueueProcessingFargateService	Service + SQS queue + DLQ

To prevent double-monitoring, the bare FargateService visitor skips services whose ancestor chain contains one of the L3 pattern constructs — those are already covered by the dedicated visitors.

Why

MonitoringFacade already exposes all of the Fargate monitoring methods, but none of them were reachable through MonitoringAspect. Teams that use the aspect for fleet-wide auto-monitoring had to opt Fargate services in manually. This change closes that gap and mirrors the wiring pattern already used for Lambda, API Gateway, DynamoDB, etc.

Changes

• lib/facade/IMonitoringAspect.ts
  • Add FargateServiceAspectType, LoadBalancedFargateServiceAspectType, QueueProcessingFargateServiceAspectType.
  • Add fargateService, fargateLoadBalancedService, queueProcessingFargateService to MonitoringAspectProps.
• lib/facade/MonitoringAspect.ts
  • Add monitorFargateService, monitorFargateLoadBalancedService, monitorQueueProcessingFargateService visitors.
  • Add isInsideFargatePattern helper to de-duplicate the bare-service match inside L3 patterns.
• lib/monitoring/aws-ecs-patterns/FargateServiceMonitoring.ts
  • Export BaseFargateServiceMonitoringProps and BaseLoadBalancedFargateServiceMonitoringProps so they can be used as aspect-option types (jsii requires named interfaces; Omit<> transforms aren't accepted).
• lib/monitoring/aws-ecs-patterns/misc.ts
  • Add BaseQueueProcessingFargateServiceMonitoringOptions as a public alias over the package-private BaseQueueProcessingServiceMonitoringProps, for the same reason.
• API.md — regenerated by projen.

Usage

new MonitoringAspect(facade, {
  fargateService: {
    props: {
      addCpuUsageAlarm: { Warning: { maxUsagePercent: 80 } },
    },
  },
  fargateLoadBalancedService: {
    props: {
      addHealthyTaskCountAlarm: { Critical: { minHealthyTasks: 1 } },
    },
  },
  queueProcessingFargateService: {
    props: {
      addQueueAlarms: { addApproximateNumberOfMessagesVisibleAlarm: { Critical: { maxMessageCount: 1000 } } },
    },
  },
});

Testing

• yarn build passes locally (compile + test + eslint + jsii assembly + pacmak for js/java/python/dotnet/go).
• New visitors mirror the established pattern in the class; no existing tests were modified.

Out of scope

• Ec2 service / Ec2-patterns variants — could be added as a follow-up with the same pattern (bare Ec2Service + L3 patterns with ancestor-skip logic).