DOCS: Update to https://docs.starlingx.io/introduction/consuming.html

[Greg Waines]

The following page:
https://docs.starlingx.io/introduction/consuming.html

Needs to be re-worded as follows:

Consuming StarlingX
-------------------
StarlingX is ready for you to use today, however, limitations exist regarding what you can do with the open source software and Starlingx Community ISO builds. Software features like secure boot, live software update/patching and live software upgrades are not fully enabled by the community.

The community does not provide signed software images, which are needed to enable features that depend on signed images to implement security features such as UEFI Secure Boot. Providing signed images is typically the responsibility of commercial vendors or the users themselves.

The commuity does not provide software updates/patches (i.e. for bug fixes or new CVE vulnerabilities) to STX released ISOs.

The community does not support or test software upgrades from one STX Release to the next STX Release. Very often for software upgrades to work from STX Release N (old/existing) to STX Release N+1 (new), a software-upgrade-enabling 'update/patch' is required for STX Release N. Because the StarlingX Community does not provide/build software updates/patches, this patch is not available from the StarlingX Community, and therefore software upgrades may not necessarily work and are not tested by the StarlingX Community.

Here are three ways in which you can consume StarlingX.

Deploy the open source code
---------------------------
You can use the open source software directly. Our community partner CENGN provides a StarlingX mirror with ready to run ISO images of the current StarlingX releases and daily builds. View the CENGN StarlingX mirror.

As previously mentioned, these images are not signed and thus do not support secure boot. Also as previously mentioned live software updates may not necessarily work without software patches, that are not currently provided by the StarlingX Commuity.

The StarlingX community recommends that users planning to deploy the open source software use the release images, which have been tested and validated by the community.

Developers planning to work against the tip of the source trees typically use the daily builds.

Deploy an internal version of StarlingX
---------------------------------------
If you are part of a company, the company itself can create a team to create their own version of StarlingX for internal use. Such a team can do acceptance testing of the open source software, customize it as needed, sign their own internal images (to enable features such as UEFI Secure Boot), and build/deliver software updates/patches that will also enable testing & support of software upgrades.

Deploy code from a vendor
-------------------------
You can consume a commercial vendor’s StarlingX-based product or solution. Vendors provide signed images and support for software updates/patches and software upgrades. They may also add features or content to the open source software and they may provide other services such as technical support.

The StarlingX community expects several vendors to provide StarlingX-based products and solutions. We hope to see more as our community grows.