Upstream OpenSSL wrap

Nobody has claimed this yet.

Conversation at https://github.com/openssl/openssl/issues/16812 finally converged on considering to add official (optional for now) Meson support upstream.

There are two major steps seeing there:
* [ ] https://github.com/openssl/openssl/issues/16188 that will serve as a single source of build sources for multiple build systems without relying on Perl when compiling from official OpenSSL release
* [ ] https://github.com/openssl/openssl/issues/16812 to use ^ for Meson build system

Essentially right now OpenSSL build system uses a non-trivial generator to figure out what sources and other things should be used depending on target platform, which causes challenges for end users trying to compile it, especialy when they don't want to rely on Perl.

By abstracting it in reusable way and generating during release process upstream, it would be much easier to pick pre-generated files by secondary build system like Meson.

Creating this issue downstream as this is where most of knowledgable engineers are who already maintain OpenSSL wrap.

I do not have the time to do this myself in the near term, but happy to collaborate with someone/help with review to make sure things are moving forward.

Start by reading the linked OpenSSL issues 16188 and 16812, then review how the downstream OpenSSL wrap currently handles generated sources and platform-specific build inputs. Done means the upstream work has converged and the wrap can consume the resulting reusable, pre-generated sources for optional Meson support without requiring Perl.

Written by the indexing model from the issue text.