Semantic highlight and document symbols on slang 0.10

[antico5]

This PR includes support for two new language features, semantic highlighting and document symbols (project outline).

It achieves so by making use of the latest version of slang (0.10.1)

These are some key points from this PR:

• I noticed that accessing nodes and properties from the CST through slang takes a lot of time, probably because it interfaces through napi. So I store some of this information on a SlangNodeWrapper object that keeps the data on the node process after reading it just once.
• Features are enabled only on supported platforms (os and architecture). Regardless, all user's platforms are now registered in sentry so we can have some insight on platforms slang should be targeting.
• The features have been rewritten using the new Cursor api from slang, versus the old custom walking method implemented on the extension side.
• Feature flags were implemented. The way they work is by fetching a json file in a given github repo/branch (currently https://raw.githubusercontent.com/antico5/hardhat-vscode/flags/flags.json). The numbers should be between 0 (0%) and 1 (100%). These flags are re-fetched on each server initialization. To determine if a given user should have the feature enabled, their machine id is hashed using MD5 and the last 2 bytes are taken. Then they are divided by 65535 and the percentile is used. This way, when a given flag is changed e.g. from 0.1 to 0.2, all users that have it previously enabled will continue to do so.
• The features are now error tolerant because of the new version of slang.

Closes #217 Closes #42 Closes #491

[socket-security[bot]]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@nomicfoundation/slang	0.10.1	None	+9	41.8 MB	nomic-foundation-publisher

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (development@aac6f3a). Click here to learn what that means.

:exclamation: Current head 4ce5653 differs from pull request most recent head 76b210f. Consider uploading reports for the commit 76b210f to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## development #523 +/- ## ============================================== Coverage ? 52.66% ============================================== Files ? 228 Lines ? 5317 Branches ? 835 ============================================== Hits ? 2800 Misses ? 2279 Partials ? 238 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Invalid package.json	@nomicfoundation/slang	0.10.1	Location: Package overview	@nomicfoundation/solidity-language-server@0.7.2 via coc/package.json server/package.json

Next steps

What is an invalid package.json?

Package has an invalid package.json and can cause installation problems if you try to use it.

Fix syntax errors in the invalid package.json and publish a new version with a valid package.json. Consumers can use npm overrides to force a version that does not have this problem if one exists.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore @nomicfoundation/slang@0.10.1