Worker friendly custom step templates

The blog post discusses the introduction of a feature that allows referencing packages within script steps, enhancing deployment processes by eliminating the need to first push a package to a target. This feature, originally introduced by Michael Richardson, simplifies the process by enabling the direct execution of scripts on Octopus servers or workers. The post explains how custom step templates can dynamically reference packages by assigning the package ID to a step template parameter, allowing access to extracted package files for further actions. It also addresses challenges with deploying specialized software, such as SSIS packages, which require specific modules not natively available on workers. To tackle this, the post suggests using the PowerShell Gallery to install necessary modules at deploy-time, ensuring compatibility by downloading and adding modules dynamically. This process includes setting up a temporary folder, checking for module installation, downloading and importing missing modules, and ensuring the availability of necessary assemblies, ultimately making deployment processes more efficient and adaptable.