Feature request: Content versioning improvement - have action parameters versioned

1. currently it is impossible to run action against older content_version if the latest action version has incompatible parameter changes (namely when required parameters was added, some parameter was deleted etc.)

2. content_version as input on action overview so that user can get action parameters as they were valid for the version specified

I recognize that would have implications (in web ui etc.)

Use case (please advice work around solution if any available): there is a pack maintained by another team and we would like to fix our application with it's "stable" version. The concept content_version seems to be great but the pack maintainers can (and probably will) change actions' parameters which would break our executions (we would run with "stable" content_version but against "latest" parameters).

We can workaround point 2. by pulling action yml from their git tag directly etc. but we are not able to execute "stable" version of pack if "latest" action has different params.

No files or tests are named. Start by mapping how content_version selects action definitions and parameters during execution and in the action overview; define behavior for added, deleted, and newly required parameters, including the web UI implications, before implementation.