(gen2-migration) `notifications` category

### Is this feature request related to a new or existing Amplify category?

_No response_

### Is this related to another service?

_No response_

### Describe the feature you'd like to request

Add support to the migration tool for the notifications category. This includes both code generation and refactor.

### Describe the solution you'd like

We are going to use [cdk-from-cfn](https://github.com/cdklabs/cdk-from-cfn) in order to generate CDK code that we will then hookup into the amplify backend using `backend.createStack('notifications')`.

### Describe alternatives you've considered

None

### Additional context

https://docs.amplify.aws/gen1/android/sdk/push-notifications/getting-started/

### Is this something that you'd be interested in working on?

- [ ] 👋 I may be able to implement this feature request

### Would this feature include a breaking change?

- [ ] ⚠️ This feature might incur a breaking change

Start with the migration tool and the cdk-from-cfn approach described in the issue. Trace how generated CDK code would be connected through backend.createStack('notifications'), using the linked Gen 1 Android push-notifications documentation for the category requirements. Done means notifications migration supports both code generation and refactoring.

Written by the indexing model from the issue text.