don't retain port in CRSessionClient, remove singleton pattern

[turbocrime]

Description of Changes

CRSessionClient of @penumbra-zone/transport-dom no longer retains a MessagePort and no longer uses a singleton pattern.

Related Issue

fixes #1736

Checklist Before Requesting Review

Tested in combination with other work, not yet tested alone.

• I have ensured that any relevant minifront changes do not cause the existing extension to break.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 90707e8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[TalDerei]

this is great! went through the CRSessionClient connection flow and left a comment about addressing listener leaks.

[TalDerei]

changed base branch to connection-lifecycle-branch

we can think more about handling memory leaks separately in the reconnection PR.