feat(service-worker): allow specifying maxAge for entire application

[henry-alakazhang]

This commit adds an applicationMaxAge to the service worker configuration. When set, it will only assign a cached version to clients within the maxAge. Afterwards, it will ignored any expired application versions and fetch exclusively from the network. The default is undefined, for which the behaviour is the same as it currently is.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: #39266

The index file (and therefore all application navigations) are cached indefinitely by the service worker.

What is the new behavior?

An optional applicationMaxAge field in the service worker ignores the cache for all requests for versions older than that age.

Does this PR introduce a breaking change?

• Yes
• No

(field is optional)

Other information

[henry-alakazhang]

Wasn't sure exactly what API to use / where to put it - I've put it in the AppVersion fetch, but the logic could live the driver.ts as well.

Linked issue could also be solved by setting maxAge on asset groups, I think, but that felt a bit roundabout for dealing with navigation requests, and might also require a bit of refactoring / duplication because the logic already exists for data groups.

[henry-alakazhang]

Hmm, I've realised that this doesn't work properly if the service worker process is shut down, as it will recreate the state and reset installTime. Instead this probably needs to use the manifest timestamp or persist the lastUpdateCheck to the DB

[thePunderWoman]

@henry-alakazhang Sorry this never got a code review. We think it's a reasonable change. Can you rebase? I'll take a look after you're able to do that.

[henry-alakazhang]

Sure, I've updated the PR (hopefully I rebased everything correctly and these things are all still in the right place).

[henry-alakazhang]

Hi @thePunderWoman, would you be able to take a look at this now?

[thePunderWoman]

LGTM! Thanks for your contribution!

[thePunderWoman]

Caretaker note: this is safe to merge with current approvals as it was discussed during a triage meeting.

[AndrewKushnir]

This PR was merged into the repository by commit 8ddce80.

The changes were merged into the following branches: main

[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.}