feat: add script execution after the rule validation

[andrea-deri]

This PR permits to handle the configuration of business logic execution using dedicated scripts.
The main information about the logic is defined in this PR, this one is related only to the configuration APIs that includes the new information in the existing interfaces.

List of Changes

• Updated interface and persistence logic, including references to scripting binding
• Added dedicated entity that maps the collection used for store script code to be executed by engine
• Added information on MockRuleEntity that permits to refers to script code to be executed in runtime
• Added new API for retrieve all script metadata that can be assigned to mock rule

Motivation and Context

This modification broadens the use cases in which Mocker can be used, adding dynamic logic that can simplify and add expressiveness to tests.

How Has This Been Tested?

• Tested in local environment

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

This PR exceeds the recommended size of 400 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.

[github-actions]

Comment this PR with update_code to format the code. Consider to use pre-commit to format the code.