Support Thirdparty runner input toggle

[tundeaoni]

No description provided.

To fix this code injection issue, you should avoid passing direct ${{ inputs.context }} expression syntax to the context: field. Instead, assign the user-controlled input to an environment variable within the respective job/step, and then refer to that environment variable using shell or action syntax that avoids possible injection issues. For third-party actions such as docker/build-push-action, the context parameter must either be interpolated safely or referenced via a shell environment variable. The recommended solution is to set CONTEXT: ${{ inputs.context }} as an environment variable at the job level, then refer to it in context: $CONTEXT (shell variable syntax) or whatever syntax is supported by the third-party action for environment variable interpolation. If the action doesn't automatically substitute env vars in its parameters, add a preceding step using run: to safely create and export the context or otherwise sanitize it. This change must be applied to both blocks using docker/build-push-action and the analogous block for useblacksmith/build-push-action.

Required changes:

• Add an environment variable CONTEXT: ${{ inputs.context }} in the job's env: section.
• Change the context: field in both relevant with-blocks to use $CONTEXT instead of ${{ inputs.context }}.