Support trackALAlertsInGitHub for workspace compilation build path (#2331)

### ❔What, Why & How

`trackALAlertsInGitHub` surfaces AL compiler diagnostics as GitHub code
scanning alerts, but it only worked on the classic Run-AlPipeline build
path. When `workspaceCompilation` (preview) was enabled, no
`*.errorLog.json` files were produced, so no alerts appeared even with
the setting turned on.

This wires the same behavior into the workspace compilation path. When
both `trackALAlertsInGitHub` and `workspaceCompilation` are enabled,
AL-Go passes `--errorlogdirectory` to `altool workspace compile` so each
project emits an `*.errorLog.json` diagnostics file into its
`.buildartifacts/ErrorLogs/` folder. From there the existing upload +
`ProcessALCodeAnalysisLogs` pipeline picks them up, converts them to
SARIF, and publishes code scanning alerts, matching the classic build
behavior.

The `--errorlogdirectory` argument is threaded through via a
`GenerateErrorLog` switch driven by `$settings.trackALAlertsInGitHub`.
If the consumed compiler version does not yet support
`--errorlogdirectory`, the option is skipped and a warning is logged so
the rest of the build is unaffected (no silent no-op, no hard failure).

### ✅ Checklist

- [x] Add tests (E2E, unit tests)
- [x] Update RELEASENOTES.md
- [ ] Update documentation (e.g. for new settings or scenarios)
- [ ] Add telemetry

---------

Co-authored-by: aholstrup1 <aholstrup1@users.noreply.github.com>