feat(cb2-10920): Angular 16 to 17

[pbardy2000]

Upgrade angular 15 to 17

CB2-10920

Checklist

• Branch is rebased against the latest develop/common
• Code and UI has been tested manually after the additional changes
• PR title includes the JIRA ticket number
• Squashed commits contain the JIRA ticket number
• Delete branch after merge

[naathanbrown]

Happy with this, but I believe the bump to 16 introduced a bug.

in the console

Quick look online led me to https://stackoverflow.com/questions/76429842/how-to-find-after-angular-upgrade-16-ng0600-writing-to-signals-is-not-allowed and appears to be a 16 introduction.

I've not really looked any further, but if it's easy reckon we could slip it in with this? Saves us writing a ticket etc. Again if it's hard ignore and go ticket path

[pbardy2000]

Happy with this, but I believe the bump to 16 introduced a bug. in the console

Quick look online led me to https://stackoverflow.com/questions/76429842/how-to-find-after-angular-upgrade-16-ng0600-writing-to-signals-is-not-allowed and appears to be a 16 introduction.

I've not really looked any further, but if it's easy reckon we could slip it in with this? Saves us writing a ticket etc. Again if it's hard ignore and go ticket path

Cheers for that, that page linked to this github issue ngrx/platform#3892 (comment), so I've just applied the fix they suggested which seems to have worked. I think the issue probably arises from the fact that we have a pipe doing a lot of data fetching and interacting with the store which is a bit strange to me but don't want mess around with it too much.