fix(angular): generate event type with inline types

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• [x] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
• [x] Build (npm run build) was run locally for affected output targets
• [x] Tests (npm test) were run locally and passed
• [x] Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• [x] Bugfix
• [ ] Feature
• [ ] Code style update (formatting, renaming)
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] Documentation content changes
• [ ] Other (please describe):

What is the current behavior?

When adding a custom event with an inline type:

@Event() ionSwipe!: EventEmitter<{ side: Side }>;

The generated event type is invalid:

 ionSwipe: EventEmitter<CustomEvent<IIonItemOptions{ side: IIonItemOptionsSide }>>;

There are two issues:

1. The nested type argument is formatted incorrectly (missing <).
2. The evaluated type shouldn’t include IIonItemOptions.

Expected output is:

ionSwipe: EventEmitter<CustomEvent<{ side: IIonItemOptionsSide }>>;

Issue URL: N/A

What is the new behavior?

• The generated event type will account for inline-types.

Does this introduce a breaking change?

• [ ] Yes
• [x] No

Other information

Dev-build: 0.0.1-dev.11705624885.1949250b