fix: install openssl@3 when building wws in actions

[Angelmmiguel]

When releasing wws v1.3, the artifacts action was failing for macOS. The issue was related to the openssl crate upgrade on #132.

This is the error message from the job:

  Could not find directory of OpenSSL installation, and this `-sys` crate cannot
  proceed without this knowledge. If OpenSSL is installed and this crate had
  trouble finding it,  you can set the `OPENSSL_DIR` environment variable for the
  compilation process.

  Make sure you also have the development packages of openssl installed.
  For example, `libssl-dev` on Ubuntu or `openssl-devel` on Fedora.

  If you're in a situation where you think the directory *should* be found
  automatically, please open a bug at https://github.com/sfackler/rust-openssl
  and include information about your system as well as this message.

  $HOST = x86_64-apple-darwin
  $TARGET = aarch64-apple-darwin
  openssl-sys = 0.9.90

Based on the openssl crate documentation, you need to install OpenSSL to build it. I assume the action runner was installing and old version that it's no longer valid for the crate and we need to explicitly install the latest one.

[Angelmmiguel]

To fix this, I tried several approaches, from installing architecture-specific packages with brew to set the OpenSSL location. After checking for multiple issues around, I found that OpenSSL is specially difficult to integrate in projects that targets multiple platforms. Even the cross team removed OpenSSL because it was difficult to maintain. That was another approach I wanted to try 🥲.

Finally, I decided to make the openssl vendored feature available as a wws feature. This approach allow us to toggle the vendored flag under demand. Before, it was automatically enabled for certain targets.

This PR / issue is another one on the "OpenSSL" related issues archive. I believe we should move to rust-tls sooner than later.

[Angelmmiguel]

I removed the artifacts action condition to run it on pull requests (I added it for testing). Here you have a successful action that created all the artifacts: https://github.com/vmware-labs/wasm-workers-server/actions/runs/5411363945

[ereslibre]

LGTM, thanks @Angelmmiguel 👏