feat(store-devtools): change connectOutsideZone to be 'true' by default

[va-stefanek]

PR Checklist

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:

Closes #4093

Does this PR introduce a breaking change?

[x] Yes
[] No

[netlify]

✅ Deploy Preview for ngrx-io ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	6de0a2a
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/6544e4c95bcb3b0008722a76
😎 Deploy Preview	https://deploy-preview-4103--ngrx-io.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[timdeschryver]

From an API perspective I don't like having booleans default to true.
Since we're going to provide a migration, could we also rename this property?
Maybe connectInsideZone, with the default value of false.

The migration will add connectInsideZone: true to the config.

[timdeschryver]

Why is this added?

[timdeschryver]

cc @brandonroberts , @markostanimirovic what do you think of a rename?

[brandonroberts]

cc @brandonroberts , @markostanimirovic what do you think of a rename?

I think your points are reasonable, and the upgrade migration would cover existing projects.

[timdeschryver]

@va-stefanek sorry, but can you rename the property to connectInsideZone (with the default value of false)?

[markostanimirovic]

cc @brandonroberts , @markostanimirovic what do you think of a rename?

Agree 👍 IIRC, I initially proposed the connectInZone name for this property.

[timdeschryver]

connectInZone also works for me 👍

[timdeschryver]

Thanks @va-stefanek