LSP Optimization: Use rayon for parse_ast_to_typed_tokens function

[JoshuaBatty]

Description

Traversing the typed tokens from sway-lib-std now goes from 3.957833ms → 1.372ms. Collecting typed tokens on the benchmark project goes from 139.6ms → 127.7ms.

I noticed that there are transient contentions when reading items from the TokenMap with this change. As such, I've implemented a new function on the TokenMap called try_get_mut_with_retry. This method tries to access the value up to 8 times if the lock is still held using the backoff and retry pattern.

related to #5445

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.

[tritao]

How come collecting typed tokens is taking 127.7ms? Or does that figure include parsing and type checking already?

[JoshuaBatty]

How come collecting typed tokens is taking 127.7ms? Or does that figure include parsing and type checking already?

This is how long it's taking to traverse and collect the tokens from the typed AST nodes. I'm going to look at using rayon par_iters for this section like we are doing in the traverse::parsed_tree module. Should hopefully take us down closer to 12ms or so.

Edit, i've managed to get it down to 14.8ms in this PR -> #5487