Add specific file loading path support to pe-bolt-modules

[lucywyman]

Use Case

In order to eventual use specific file paths (module/files/myfile.txt and module/scripts/myscript.sh) over nonspecific file paths (module/myscript.sh) we first need to add support for the new file path loading syntax in the Orchestrator. Because the Orchestrator doesn't load Bolt configuration - and because the feature has been introduced with a future flag for a while - the following precedence for loading scripts will be default in both Orchestrator and Bolt:

When passed module/myscript.sh

• files/myscript.sh

When passed module/scripts/myscript.sh:

• Look first in files/scripts/myscript.sh
• Then fall back to scripts/myscript.sh

When passed module/files/myscript.sh:

• files/files/myscript.sh
• files/myscript.sh

This issue encompasses removing the future flag (without erroring or warning - we can just ignore it) and applying changes made as part of #2760 to Bolt plan functions to the pe-bolt-modules functions. Those functions should continue to not load from absolute paths.

Relies on #2920