Support job_token_scope configuration

[hertzsprung]

GitLab provides a PATCH request to enable or disable a project's job_token_scope.
But, as far as I'm aware, this is not yet supported by gitlabform.

[amimas]

Hello. I believe this is same/duplicate of issue #571 . Could you please confirm?

[hertzsprung]

It's closely related, feel free to combine the two issues if appropriate. But the PATCH request only sets a boolean flag for the project, it doesn't allow fine grained control provided by the allowlist.

[amimas]

the PATCH request only sets a boolean flag for the project,

Thanks for clarifying. I think it's fine for this to be a separate issue. Can be implemented without everything related to job token being involved. Keeps the scope small.

PRs are welcome. Would you be able to help contribute this feature? Do you have a proposal for the config syntax?

[hertzsprung]

Makes sense, thanks. I'll get back to you next week with a config syntax proposal that accommodates #607 and #571. If we're happy I'll try to find time to contribute, too.

[amimas]

That sounds great!! Thanks.

[TimKnight-DWP]

@amimas @hertzsprung changes to support this are here: TimKnight-DWP#1

Currently on my fork only because I need to point at my fork of python-gitlab to pick up that part of the chain. Everything is capable of being merged when gitlab 16.10 gets released, so I'll update the MR to point back to mainline python-gitlab when this MR goers in python-gitlab/python-gitlab#2816.

However a review of the proposed changes would be great if possible :)