Fix release pipeline

[rijkvanzanten]

The improved build/release pipeline has a couple critical issues:

• npm isn't authenticated as the correct user in the lerna publish step
• the ARM docker image fails building
• node-oracledb prevents image from being built

ref: #6759, #6796

@paescuj It seems like SQLite is trying to build the native dependencies from source, but fails doing so as Python isn't available on the image

cc @SeanDylanGoff @nickrum FWIW, the NPM token in the repo secrets is an Automation Token tied to my account.

[SeanDylanGoff]

@rijkvanzanten OK let's debug the NPM issue first. I just tested with my own token, with this code: https://github.com/cynova/directus/blob/build-test/.github/workflows/release.yml
Can you maybe run this aswell? Should take < 1 min and we can exclude one possible error.

[rijkvanzanten]

Should take < 1 min

It does mean pushing out new tags etc, not the quickest to do unfortunately.

Would it be easier to add a new action that has a manual trigger just to check the npm whoami?

[SeanDylanGoff]

Should take < 1 min

It does mean pushing out new tags etc, not the quickest to do unfortunately.

Hmm OK true especially without messing up the history.
I used git add --all && git commit -m test && git push && npx lerna version --exact --force-publish --yes patch to test quickly.

Would it be easier to add a new action that has a manual trigger just to check the npm whoami?

I guess that would also work

[SeanDylanGoff]

@rijkvanzanten About ARM: Should we maybe just disable this for now?
Not sure if holding back rc-84 for it makes sense as there could be heaps of errors after the current one...

[rijkvanzanten]

Yeah, might not be a bad idea, though... I think oracle, sqlite, and argon2 are the main dependencies that have a deeper native binding that needs building, so it might be worth fixing for Sqlite, and checking where that puts us