[refactor]: Add method to define parameter in executor migrate entrypoint

[dima74]

Description

• Added method add_parameter which can be called from executor (in migrate entrypoint) to define new executor parameter
• Added test which demonstrates how executor can use it, as suggested here
• Note that this PR was mostly implemented before discussion in dynamic parameter value #4352, so potentially this should be implemented differently. E.g. if it will be decided to store executor parameters in Domain::metadata, then there will be no need for add_parameter method since executor parameter will be defined using SetKeyValue ISI
• Note that I didn't removed NewParameter ISI since it is currently used to define chain-wide parameters (for wasm engine and sumeragi), and potentially chain-wide parameters should be defined/stored differently as discussed in dynamic parameter value #4352 (comment)

Linked issue

Closes #3901
Related: #4352
Related: #4310

Benefits

Checklist

• I've read CONTRIBUTING.md
• I've used the standard signed-off commit format (or will squash just before merging)
• All applicable CI checks pass (or I promised to make them pass later)
• (optional) I've written unit tests for the code changes
• I replied to all comments after code review, marking all implemented changes with thumbs up

[mversic]

superseeded by #4597

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification, and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "[refactor]: Add method to define parameter in executor `migrate` entrypoint". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit