Migrate blueprints to v9.

[mshima]

Overview of the feature request

In preparation for final v9 we should migrate blueprints to v9.

A few fixes were deployed before beta.3 to fix blueprint support:

• e2d88c1
• yeoman-environment 5.1.3

Blueprints:

• entity-audit

Motivation for or Use Case

Related issues or PR

• Checking this box is mandatory (this is just to show you read everything)

[DhairyasheelS]

Hi, I’d like to work on migrating blueprints to v9.
I recently contributed to the Angular generator (PR #32359 – aligning User Management UI with standard entity templates, closes #31891), so I’m familiar with the generator layout and contributing flow.

Before I start, could you clarify:

Scope: Should I focus on a single blueprint first (e.g. entity-audit), or is the goal to migrate multiple blueprints in this issue?

Definition of “migrate”: What should be done for each blueprint (e.g. update to yeoman-environment 5.1.3 / v9 APIs, fix breaking changes from beta.3, run tests, something else)?

Happy to start with entity-audit if that’s the preferred first step.