Expose JTE Primitives via GlobalVariables instead of the TemplateBinding

[steven-terrana]

PR Details

This PR hopefully fixes #188 and all cases of

java.lang.UnsupportedOperationException: Refusing to marshal * for security reasons;

Description

Until now, all JTE Pipeline Primitives like steps, stages, keywords, application_environments were instantiated as objects and stored in a common TemplateBinding.

This TemplateBinding was needed several times in different contexts and was therefore stored as an InvisibleAction.

Objects serialized via Actions are subject to JEP-200 which meant that we needed to maintain a custom ClassFilterImpl.

This quickly grew unmanageable as it meant that any user defined variable in the binding would need to be added to the ClassFilterImpl.

This PR resolves the issue by demoting the role of TemplateBinding to that of a runtime collision detector and instead surfaces TemplatePrimitives via a GlobalVariableSet.

Overall, this was a pretty substantial PR:

50 files changed, 1526 insertions(+), 2496 deletions(-)

Fortunately, the change actually simplified JTE internals a bit.

How Has This Been Tested

Used myself for a week or so. Unit tests continuing to pass.

Types of Changes

• Docs change / refactoring / dependency upgrade
• Added Unit Testing
• 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 change)

Checklist

• I have added the appropriate label for this PR
• If necessary, I have updated the documentation accordingly.
• All new and existing tests passed.