Automatically verify release Teleport binaries

[codingllama]

What would you like Teleport to do?

Replace various manual binary checks with automation, including but not limited to:

• List of dynamic dependencies
• Required glibc version
• Presence of (static) libfido2 for tsh (Linux and macOS)
• Presence of Touch ID for tsh (macOS)

As an extra for this feature request, we should exercise delivery pipelines in regular builds, to make sure they are in good shape and produce binaries that pass the criteria above.

(If you have other requirements in mind, please edit the list above.)

What problem does this solve?

It avoids surprises during release testing and increases confidence in release binaries.

If a workaround exists, please include it.

Not applicable.

[codingllama]

FYI @tcsc @zmb3, dropping an important part of my personal wishlist right here. :)

I would take this as an opportunity to "revamp" (as in delete and start fresh) our release pipelines, so they are simpler and can easily be executed locally or during regular builds (meaning we don't necessarily have to do the final push step).

[zmb3]

Marking as duplicate of #4857