AgentCore resource observability traces and application/usage logs disabled by default

## Description

The AgentCore CLI automatically enables CloudWatch Transaction Search for Python runtime deployments. However, it does not provide a CLI-native way to configure CloudWatch vended-log deliveries for AgentCore resources.

Some observability data requires explicit delivery configuration, including runtime usage logs and application logs for resources such as Memory, Gateway, and Identity. Users currently need to configure these destinations manually through the AWS console or SDK.

## Current Behavior

- Transaction Search is automatically enabled for supported Python runtime deployments.
- Built-in metrics and runtime service logs are available where provided by the service.
- Vended-log delivery sources, destinations, and deliveries are not configured by the CLI.
- There is no project configuration or CLI command for selecting log types and destinations.

## Expected Behavior

Provide a CLI-native way to configure CloudWatch vended-log deliveries for AgentCore resources. This could be supported through project configuration, deployment options, or dedicated commands.

The configuration should support applicable log types such as:

- Runtime `USAGE_LOGS`
- Memory and Gateway `APPLICATION_LOGS`
- Logs for other supported AgentCore resource types

Users should be able to select or configure a destination and apply the configuration during deployment without needing to use the AWS console or SDK.

Inizia tracciando i punti di ingresso della CLI per la configurazione del progetto e il deployment, quindi esamina come CloudWatch vended-log sources, destinations, and deliveries vengono applicati alle risorse AgentCore. Definisci i tipi di log supportati e la configurazione della destinazione, quindi verifica che il deployment li applichi senza passaggi nella console o nell'SDK.

Scritto dal modello di indicizzazione a partire dal testo della issue.