ci: fix arm64 linker errors

[strophy]

Issue being fixed or feature implemented

Building this package failed in CI with the error: linking with `cc` failed: exit status: 1 or similar.

What was done?

Explicitly specify which linker to use for this target and make sure it is installed in build environment.

How Has This Been Tested?

• Clone dashevo/platform on arm64 device, run yarn install --> fails with rs-drive dep error, "No native build was found"
• Clone strophy/platform on arm64 with strophy/rs-drive npm dep, run yarn install --> success

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[strophy]

This is a bit of a hack because we are repurposing a musl build container to build a gnu binary. All the gnu compilers are present in the x86_64 musl build image though, so I'm not sure why it's not there on arm64. As an alternative, we could change the action to not use a docker container to build instead, but this solution is more simple and consistent with the x86_64 build step.

[shumkov]

Good job! 👍