Fix action manifests

[kariharju]

Description

At some point the action manifest logic lost the history versions of the action packages

Added a renegeration logic that rebuilds the manifest based on S3 content and whitelist json.

This is a manual process as we should not need to do this, basically ever.
This requires downloading the S3 actions folder content locally

The update scripting was/is working correctly, but as it relies on the manifest.json, if a broken manifest gets published the update keeps building on top of that.

• Dropped the sai manifest generation that was confusing the logic.
• Dropped "build all packages" as that would break the manifest totally (potential reason for this)
• Unprettified the result JSONS (json size from 1,5MB to 800KB) affects Studio responsiveness directly.

How can (was) this tested?

Studio before:

Studio after (not linked):

Studio after (SF linked):

Screenshots (if needed)

Checklist:

• I have bumped the version number for the Action Package / Agent
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation - README.md file
• I have updated the CHANGELOG.md file in correspondence with my changes
• I have added tests that prove my fix is effective or that my feature works
• OAuth2: I have made sure that action has necessary scopes (works in whitelisted mode)

[kariharju]

@codex review

[mmokko]

Added some comments to make the code a bit safer. Consider using os.walk or os.scandir instead of os.listdir for efficiency.

I'll approve this regardless of comments. There were no immediate issues that I found.