meta(extensions): tracking issue for extensions / plugins

[zerosnacks]

Tracking all tickets related to extensions / plugins or proposed extensions:

Previous discussion

• Plugin system #706
• Forge Extensions #6509
• Support for foundry plugins written in Rust #7760

Extension ideas

• Add forge lint #1970
• Integration of Foundry Plugin for IntelliJ IDEA #5864
• Support making proposal to Openzeppelin Defender #5015
• [VSCode extension] Start test via keyboard shortcuts / macro #3714
• forge deploy feature wishlist #3911
• feat(cheatcodes): support additional cheatcodes to aid in symbolic testing #4072 (vendor-specific cheatcodes)
• Plugin system for solidity precompiles #5576
  • Add new precompiled contract for SECP256R1 signature verification #7637
• feat(forge script): preview, batch, and execute Gnosis Safe transactions (ape-safe) #1232
• feat(debugger): Debug Adapter Protocol #5784
• feat(periphery): support to invoke metamask #6556
• feat(cheatcodes): add vm.startContractBroadcast to support simulating / transaction from smart contract wallets #6564
• Support Account Abstraction in Foundry  #7128 (account abstraction)
• use a custom create2 factory
• use create3 instead of create2
• execute via a smart contract wallet
• execute via a relayer service like Gelato
• feat(forge): add support for flamegraph #7761

Alternative VMs

zxSync

• feat(compatibility): add zkSync support #7624
• proposal: implement unified interface for invoking different foundry implementations #9227

Interaction

• feat(extensions): add forge run command #8354

Repo's

• https://github.com/OpenZeppelin/openzeppelin-foundry-upgrades

[zerosnacks]

Previous discussion tickets: #706 + #7760 + #6509

Would greatly appreciate all your input and ideas around this topic to be shared here