fix(firestore, web): use enableMultiTabIndexedDbPersistence() API when the user inputs synchronizeTabs as true

[russellwheatley]

Description

Firestore web JS has changed its API from synchronizeTabs to forceOwnership. See documentation: https://firebase.google.com/docs/reference/js/firestore_.persistencesettings.md

Related Issues

fixes #9929

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[Ehesp]

Can we not just deprecate instead of forcing a breaking change?

[pldelattre]

Is forceOwnership truly the same as synchronizeTabs ?

forceOwnership description is :
Whether to force enable persistence for the client. This cannot be used with multi-tab synchronization and is primarily intended for use with Web Workers. Setting this to true will enable persistence, but cause other tabs using persistence to fail.

But the goal of synchronizeTabs was to enable multi-tab persistence, wasn't it ?

[pldelattre]

it seems the right method to call is enableMultiTabIndexedDbPersistence()
Documentation :
https://firebase.google.com/docs/reference/js/firestore_.md#enablemultitabindexeddbpersistence