User can manage "application configuration" (SSM parameters, Secrets, App Config, ...)

viewing and editing application configuration:

* AWS SSM parameters - crud and filtering operations using paths
* commonly the application configuration is located at multiple paths (eg/ shared global, app general, component specific)
* potentially re-encypting using multiple KMS keys, one for each key edited
* AWS Secrets Manager - crud/filtering operations using path separators "/"
* kicking off rotation
* AWS App Config - crud operations for applications and envs
* filter by app

Start by scoping the three requested AWS areas: SSM parameters, Secrets Manager, and App Config. Define the required CRUD, filtering, path handling, key re-encryption, rotation, and application/environment operations before locating the relevant extension entry points. Done means the issue's requested configuration-management workflows are implemented and verified.

Written by the indexing model from the issue text.