Evaluate legacy method of setting NX CI Access Token

[tobiashofmann]

Seems that the NX CI access token is included in nx.json: https://github.com/SAP/open-ux-tools/blob/main/nx.json

"accessToken": "ZjFiYzA4OTYtYjFlNS00NTI2LTk4OTktNWZiYTAyMGE0ZGRmfHJlYWQtd3JpdGU=",

This is considered legacy by NX: https://nx.dev/ci/recipes/security/access-tokens

"We do not recommend that you commit an access token to your repository but older versions of Nx do support this"

Why not use secrets and put the token there? Seems that the token used in a read/write token:
f1bc0896-b1e5-4526-9899-5fba020a4ddf|read-write

The NX documentation cited above states additional recommendation for a read/write token.

In case the token is still used: why not follow the NX recommendations?
If not used: why not remove it?

[devinea]

Thanks. Investigating.