fix(memoryLeak): disable cache for transitjs

[Matthew-Mallimo]

Description

We noticed a memory leak happening where if non-immutable data was put into the store, transit-js would cache all the keys for that non-immutable data. This cache persisted across calls, and would grow indefinitely.

The solution is to use transit-js directly, and disable the cache. unfortunately transit-immutable-js does not allow you to pass options to transit-js, so we have to add handles manually.

Motivation and Context

memory leaks are bad

How Has This Been Tested?

Tested independently and unit tested

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

[github-actions]

Size Change: +354 B (0%)

Total Size: 687 kB

Filename	Size	Change
./build/app/app.js	164 kB	+354 B (0%)

ℹ️ View Unchanged

Filename	Size
./build/app/app~vendors.js	389 kB
./build/app/runtime.js	7.07 kB
./build/app/service-worker-client.js	7.26 kB
./build/app/vendors.js	120 kB

_{compressed-size-action}