feature: Make web-hook specific access tokens bound to workspace

[wasnertobias]

If I create a web-hook-specific access token from a script that is selected, e.g., in a test workspace, I expect that the token is also bound to that workspace.

However, Currently, it could also be used in a different workspace without the possibility of narrowing the scope. That way, the claim "save to give away to anyone" is not given, as the isolation of the workspace is not given.