Resolve regression where library steps cannot declare a package

[steven-terrana]

PR Details

fixes #296

Description

PR #286 introduced a regression causing library steps that declare a package name to fail to compile.

We switched from setting the step's base script to a StepWrapperScript via the CompilerConfiguration to instead using the @BaseScript annotation.

This annotation was being added to the step source text by prepending the line of code.

It was this prepending that caused the compilation exception, because the package declaration must come first.

The bug is resolved by instead appending the @BaseScript annotation to the bottom of the step's source text instead.

How Has This Been Tested

unit test confirms bug and fix

Types of Changes

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