Fix AL-Go bootstrap and public repository builds

[jonaswre]

CI could not check the private AL-Go template, and the container hook crashed while reading npm credentials in this AL-only repository. Organization-wide signing settings also required credentials unavailable to this public repository.

Use Microsoft's public PTE template, remove the unused npm bootstrap, and disable app signing for this PTE. Keep the existing container setup and inherit the organization's self-hosted,AL-Go runner setting. Make existing AL method calls explicit for strict analysis and configure AL-Go to use the repository ruleset.

Validation:

• Local strict AL compilation passes with warnings treated as errors.
• Container-hook validation reproduced four failing scenarios before the fix; all four passed afterward in PowerShell 7, Windows PowerShell 5.1, and an earlier hosted run. No test scripts or dedicated test workflow are included in this PR.
• CI/CD run 34595062032 passed at 2d7ea2e on self-hosted runner byndit-win-04. The app compiled and published successfully to the temporary BC container; signing was skipped and the unsigned Apps-1.0.17.0 artifact was uploaded.
• Pull Request Build run 34595063402 also passed on byndit-win-04 at the same commit.
• No AL runtime tests exist in this repository. Compilation and publication do not prove the email-log UI workflow.

Runner access was configured separately from this diff: beyondmaillog-windows permits only this repository and contains byndit-win-04. The other three runners remain in byndit-private-windows. Organization secrets were not changed. Releases promote CI artifacts and will therefore also be unsigned. The separate Update AL-Go System Files workflow still requires access to GhTokenWorkflow.