fix(ng-dev): allow deprecations in PRs during feature freeze

[josephperrott]

Currently our tooling does not distinguish between when RC is occurring and when feature freeze is occurring.
Since they are treated as the same state, we are unable to allow deprecations messages on feature freeze without
allowing it during RC periods. By creating this distinction we can properly handle this case.

[devversion]

Looks awesome 🎉

I'm slightly unhappy that the creation of the active release trains is not as obvious as before. i.e. with the object it was clear what ReleaseTrain goes into next for example, while now we have positional arguments.

[josephperrott]

@devversion Yeah, I don't love that its positional, I thought about potentially having it be the object from before that was provided as the argument. But wasn't sure if that would end up better.

So we could have

export class ActiveReleaseTrains {
  /** Release-train currently in the "release-candidate" or "feature-freeze" phase. */
  readonly releaseCandidate: ReleaseTrain | null = this.trains.releaseCandidate;
  /** Release-train in the `next` phase. */
  readonly next: ReleaseTrain = this.trains.next;
  /** Release-train currently in the "latest" phase. */
  readonly latest: ReleaseTrain = this.trains.latest

  constructor(private trains: {
    releaseCandidate: ReleaseTrain | null,
    next: ReleaseTrain,
    latest: ReleaseTrain,
  }) {}
...

[josephperrott]

This PR was merged into the repository by commit cce6d07.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}