Add some content to elaborate what "support" means for Bottlerocket

**Path to page with content (_do not_ include domain name):**

N/A - new page request

**What should the content say or communicate?**

To help folks evaluating whether Bottlerocket would meet their needs or not, it would be helpful to set some expectations on what kind of support (or responsiveness to issues, where to go to report a problem, where to go to report a feature request, etc) they can expect when using Bottlerocket.

I don't see this as an exhaustive guide for what they need to do, but at least something to help convey some of what a user can expect when using Bottlerocket and what they can expect if they need help.

No source path, test, or implementation file is identified; begin by finding how new pages and support guidance are maintained in this website. Done means publishing a page that explains expected support, issue reporting, and feature-request channels for Bottlerocket users.

Written by the indexing model from the issue text.