gen2-migration "generate" crashes with ValidationException on a wildcard EventBridge permission (SourceArn ".../rule/*")

### How did you install the Amplify CLI?

npm

### If applicable, what version of Node.js are you using?

20.19.6

### Amplify CLI Version

@aws-amplify/cli-internal-gen2-migration-experimental-alpha@0.7.0 (host @aws-amplify/cli 14.3.0) — bug is in the experimental gen2-migration alpha, not the core CLI

### What operating system are you using?

macOS

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No changes made to reproduce. The wildcard .../rule/* invoke permission exists on a Gen 1 scheduled function in our app; cloud resources were not altered to produce the bug.

### Describe the bug

Running amplify gen2-migration generate (from @aws-amplify/cli-internal-gen2-migration-experimental-alpha@0.7.0) crashes when any Lambda has a resource-based permission for events.amazonaws.com whose Condition.ArnLike["AWS:SourceArn"] ends in :rule/* (a wildcard grant, not a specific rule).

fetchFunctionSchedule in lib/commands/gen2-migration/generate/_infra/aws-fetcher.js derives the rule name by taking the segment after rule/. For a wildcard ARN that segment is the literal *. It then calls DescribeRule({ Name: "*" }), which EventBridge rejects as an invalid name with a ValidationException. The exception is unhandled and aborts the entire generate run. In our project the trigger is a scheduled function (DelayedSurveyCreation) carrying a .../rule/* permission.

### Expected behavior

A wildcard (or otherwise invalid) rule name isn't a real schedule target. fetchFunctionSchedule should treat it as "no schedule found" and continue, instead of aborting the migration.

### Reproduction steps

1. Create a Lambda `WildcardRuleFn` in any account.
2. Add a wildcard EventBridge invoke permissions:
`aws lambda add-permission \
--function-name WildcardRuleFn \
--statement-id allow-eventbridge-wildcard \
--action lambda:InvokeFunction \
--principal events.amazonaws.com \
--source-arn 'arn:aws:events:us-east-1::rule/*'`
3. In a Gen 1 project that includes this function, run `npx amplify gen2-migration generate`.
4. The command throws `ValidationException` from `DescribeRule` and aborts.

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

ValidationException: 1 validation error detected: Value '*' at 'name' failed to satisfy constraint: Member must satisfy regular expression pattern: [\.\-_A-Za-z0-9]+
at DescribeRuleCommand (…/generate/_infra/aws-fetcher.js → fetchFunctionSchedule)
```

### Additional information

Validate the extracted name against EventBridge's own pattern before the call; return undefined if it doesn't match. In aws-fetcher.js:

```
- if (!ruleName)
- return undefined;
+ if (!ruleName || !/^[\.\-_A-Za-z0-9]+$/.test(ruleName))
+ return undefined;
const ruleResponse = await this.clients.cloudWatchEvents.send(new client_cloudwatch_events_1.DescribeRuleCommand({ Name: ruleName }));
return ruleResponse.ScheduleExpression;
```

We apply this in one local patch combined with the orphan-rule fix in the related issue. Related: #14912 [https://github.com/aws-amplify/amplify-cli/issues/14912].

### Before submitting, please confirm:

- [x] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [x] I have removed any sensitive information from my code snippets and submission.

Start in lib/commands/gen2-migration/generate/_infra/aws-fetcher.js at fetchFunctionSchedule and review how the rule name is extracted before DescribeRule runs. Reproduce with the wildcard EventBridge permission and run amplify gen2-migration generate; done means the invalid wildcard is treated as no schedule and the migration continues without ValidationException.

Written by the indexing model from the issue text.