Support "parameters" in scripted pipeline job

[reinholdfuereder]

Inspired by #298 and #460 where I initially claimed that the "string" interceptor is not ideal -- that I want to take back now.

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
• Link to relevant pull requests, esp. upstream and downstream changes
• Ensure you have provided tests - that demonstrates feature works or fixes the issue

[nre-ableton]

Just two questions

[reinholdfuereder]

Thanks for your feedback: Actually I did not use these boolean parameters any further in the pipeline script (like the string parameter), because I actually only wanted to show/test the callstack output of (a) "parameters" with different parameter types ("string" interceptor for string-typed parameter), and (b) also in combination with "withCredentials" -- where I was not happen with side effects between "string" interceptor initially (maybe with JenkinsPipelineUnit v1.8; but maybe I back then already lacked the insight from my comment #460 (comment))

So no, I did not use the boolean parameters on purpose. But if you want me to use it, I can certainly add that.

[nre-ableton]

Ok, thanks for the clarification.