Initial wolfSSH Espressif Component Publish

[gojimmypi]

Similar to wolfSSL/wolfssl#6708 these are the files used to publish wolfSSH as a component to the Espressif Component Registry.

These files are not part of wolfSSH library and are only needed to publish wolfSSH to the Espressif ESP Registry:

https://components.espressif.com/components?q=namespace:wolfssl (wolfSSH not yet deployed to production site).

The staging site is at:

https://components-staging.espressif.com/components/gojimmypi/mywolfssh

Note that for the staging site, I have implemented user-specific namespace support in the install script (in my case: gojimmypi and detected with the $USER variable). Additionally, on the staging site components are renamed with a my prefix, to distinguish from production libraries. This allows multiple publishers to publish their own test components individually before using the single production wolfssl namespace and component names. This also aids in support identification if a customer is using experimental staging components.

Only Linux bash script is implemented at this time for publishing.

See the README.md for details. See also #588 and wolfSSL/wolfMQTT#352

The recent updates here include support for the staging site and passing a parameter as to the source code to install:

./wolfssl_component_publish.sh /mnt/c/workspace/wolfssl-master

See the INSTALL.md for files to edit for published version specification and other details.

Closes #588 and partially addresses #428 (a different CMakeLists.txt is needed for non-managed components). PR for that soon in separate examples.