fix: Use LRUCache for extendSessionOnUse

[dblythy]

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Currently, extendSessionOnUse functions as a debounce, and does not clear the throttle store.

Closes: #8682

Approach

• Change timeout logic (debounce) to a throttle, where the first session call is executed, and then subsequent calls do not extend
• Sessions are no longer looked up and extended if they have been pulled from the session cache, as the only way they get into the session cache in the first place, is if they have been used recently (I believe it's safe to assume they have been extended already)

Tasks

• Add new Parse Error codes to Parse JS SDK

[parse-github-assistant]

Thanks for opening this pull request!

[dblythy]

@Moumouls could you add your thoughts?

[codecov]

Codecov Report

Patch coverage: 80.00% and project coverage change: -0.19 ⚠️

Comparison is base (c9b5971) 94.37% compared to head (9de7411) 94.19%.

❗ Current head 9de7411 differs from pull request most recent head ba02bb4. Consider uploading reports for the commit ba02bb4 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##            alpha    #8683      +/-   ##
==========================================
- Coverage   94.37%   94.19%   -0.19%     
==========================================
  Files         185      185              
  Lines       14761    14758       -3     
==========================================
- Hits        13931    13901      -30     
- Misses        830      857      +27     

Impacted Files	Coverage Δ
src/Auth.js	98.46% <80.00%> (-0.40%)	⬇️

... and 4 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[mtrezza]

Is this only a perf PR or does it actually fix a bug, or both - for the changelog entry.

[Moumouls]

LGTM

[Moumouls]

Bug and perf i think @mtrezza

[mtrezza]

Then what would be a better PR title, to inform developers what the bug is.

[mtrezza]

@dblythy Could you rewrite the PR title? If the PR includes a bug fix and a perf improvement, then the PR is a fix since that is higher ranked and the perf improvement could be added as additional note.

[mtrezza]

@Moumouls Do you think you could take a look at this Auth thing as well? We just need to resolve the conflict to merge this, but not sure how to do that. If you could make a suggestion I'd commit the change.