feat: add security.json initialization as default with anchor init and integrate program-metadata to deploy the security file on-chain

[BretasArthur1]

Description

• Add as default the initialization of the security.json file under the root dir with default template.
• Integrate under the anchor program deploy the possibility to deploy the security.json file on-chain with the program-metadata-program
• Fix a CLI comment reflecting the actual implementation of the Verify feature ( I missed it when I implemented the Verify tool)

---

Tests

File generated :

File deployed

[vercel]

@BretasArthur1 is attempting to deploy a commit to the Solana Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[BretasArthur1]

Should we have a fetch security using pmp as well? (Open question)

[Woody4618]

nice!

[jamie-osec]

Can you use/refactor the existing PMP machinery?

[BretasArthur1]

Can you use/refactor the existing PMP machinery?

Ok!

[jamie-osec]

Also can you please fix the conflicts 😁

[BretasArthur1]

Hey @jamie-osec, I introduced a new MetadataCommand agnostic enum, unifying the running logic and added a new SecurityCommand enum as well to handle the security metadata machinery. Both Idl and Security now use the same running logic from MetadataCommand status() and they introduce a new method in both SecurityCommand and IdlSubcommandKind to transform them into a MetadataCommand variant.

[jamie-osec]

LGTM aside from the comments

[BretasArthur1]

addressing both asap