chore: enhance CI/CD and development workflows

[zouguangxian]

• Add comprehensive GitHub Actions workflows for CI, benchmarking, and custom actions
• Update devcontainer configuration with additional extensions and settings
• Introduce custom actions for parsing GNU time output, dumping runner stats, and setting up benchmarks
• Update Makefile with more targets and improved dependency management
• Add .editorconfig for consistent code formatting
• Update rust-toolchain to latest version (1.84.1)
• Improve dependency installation and environment setup scripts

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@actions/[email protected]	environment, filesystem Transitive: network, shell, unsafe	+6	1.57 MB	thboop
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+440	40.5 MB	simenb

View full report↗︎

[socket-security]

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

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

Alert	Package	Note	Source	CI
High CVE	npm/[email protected]	CVE: GHSA-grv7-fg5c-xmjg Uncontrolled resource consumption in braces (HIGH) Affected versions: < 3.0.3 Patched version: 3.0.3	.github/actions/parse-gnu-time/package-lock.json .github/actions/parse-gnu-time/package.json	⚠︎

View full report↗︎

Next steps

What is a CVE?

Contains a high severity Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]