feat: build lit actions and update cids when building sdk

[FedericoAmura]

Description

This PR:

1. When building the SDK => builds Lit Actions in wrapped-keys-lit-actions and updates the associated CID in LIT_ACTION_CID_REPOSITORY and LIT_ACTION_CID_REPOSITORY_COMMON
2. Before publishing the SDK => publishes lit actions code to IPFS

Both things are attached to our existing processes to enforce consistency of the built, referenced and published code

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [x] Tested triggering our current sync-actions-to-ipfs script automatically on a publish dry run
• [x] Tested building and updating references locally

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my code
• [x] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged and published in downstream modules

[Ansonhkg]

nit: I think we need to document where do we get the LIT_IPFS_JWT token and it's from Pinata