feat: apply Object.freeze in patchState on state in dev mode

[rainerhahnekamp]

Alternative version to protected the state from mutable changes via Object.freeze.

Please check if your PR fulfills the following requirements:

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

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Mutable changes in patchState don't trigger any kind of warning

Closes #4030

What is the new behavior?

In development mode (ngDevMode), Object.freeze is applied to the state, causing a runtime error on a mutable change.

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Other information

• I might be better to reuse the existing freeze function from the global store. For that, we would have to move freeze to @ngrx/operators. Maybe a follow-up PR or should I include it in the current one?

[netlify]

✅ Deploy Preview for ngrx-io canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	4216e54
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/66eadaa348f0b10008f6e09c