feat: make service log level configurable

[dvag-gloeckner-daniel]

This change introduces the feature discussed in
#150.

[github-actions]

Hi, thank you for creating your PR, we will check it out very soon

[dvag-gloeckner-daniel]

@neilime there seem to be some environmental issues regarding CI tests
https://github.com/hoverkraft-tech/compose-action/actions/runs/15158124313/job/42617806352

[dvag-gloeckner-daniel]

@neilime I think the CI pipeline does not work for PRs from forks. What's the way forward? :)

[neilime]

Can you rename service-log-level to services-log-level

Thanks

[dvag-gloeckner-daniel]

@neilime services-log-level it is :)

[neilime]

@neilime services-log-level it is :)

Thanks, can you run npm run all to be sure all is OK?

[dvag-gloeckner-daniel]

I ran npm run all. Tests are green, linter is happy, code is properly formatted.

But I forgot to update the compiled js under dist. Pushed that right now.

[dvag-gloeckner-daniel]

@neilime now we're back to the failing CI due to "Error: Failed to get odic token, did you forget the permissions: { id-token: write } permission in your caller workflow, alternatively permissions: write-all works too: Error: Error message: Unable to get ACTIONS_ID_TOKEN_REQUEST_URL env variable"

[dvag-gloeckner-daniel]

@neilime anything I could help with to fix the CI build? Maybe PRs from forks are not working in the current setup?

[dvag-gloeckner-daniel]

@neilime please have a look again :)

[neilime]

@dvag-gloeckner-daniel there is a new security blocking point with GitHub Actions:

OIDC is not available to workflows triggered by pull_request from forks for security reasons.

I've "cloned" the PR to validate it properly: #159