feat(get-platform): remove error, rephrase it as a warning

[jkomyno]

Closes #17390.

• Stop erroring out when using an unsupported arch when running Prisma on Linux Alpine
• Add link CLI utility to @prisma/get-platform

TODO

• Create a pris.ly link https://pris.ly/d/docker-alpine to the tutorial generated by (Serverless: OS Support Initiative): Document how to use Prisma with Docker / Linux Distros docs#4365

[jkomyno]

Integration PR: #17392

[jkomyno]

Decision points inspired from Slack:

1. Is this enough to detect whether Prisma is being run via custom compiled engines?

  const usesOfficialEngines = !(
    process.env.PRISMA_QUERY_ENGINE_BINARY ||
    process.env.PRISMA_QUERY_ENGINE_LIBRARY ||
    process.env.PRISMA_MIGRATION_ENGINE_BINARY
  )

2. It's easier to just output a warning and avoid the error altogether, as users realistically want to use alpine on amd64 (already supported) and arm64 (will be supported by prisma@4.10.0). So, should we remove the error altogether?

3. Should we conditionally disable the newly introduced warnings in @prisma/get-platforms given some env var, like PRISMA_DISABLE_PLATFORM_RESOLUTION_WARNINGS=1?. Some users wanted that (link), and I could see the reasoning for it

4. How do we want to frame the warning messages? We should soft them so that the users don't get scared of the new warnings, and ideally link to the docs (which don't exist yet).

[Jolg42]

@jkomyno Could you remove this binary packages/engines/introspection-engine-darwin-arm64 and force push?