Licensing Expectations document

Summary Addresses 2 issues:

1. I know license info is spread out across /charter/packages/$NAME/Architecture.md I think that being the location for license info results in a bad user experience though for 2 reasons.
   1.) It's hard for a net new user to know to look there for licensing info / poor discoverability. https://blog.louisedowne.com/2018/06/14/15-principles-of-good-service-design/ "Be easy to find"
   2.) User has to navigate through ~15 files instead of it being in 1 central location.
2. We had this page in IL2 that wasn't perfect but was decent, I'm improving upon it to have answers/info more targeted to questions of interest to customers (Do I need a license, who buys the license, what's PB using, etc.), and moving it to the public repo. (b/c we don't want to hide info when possible) https://confluence.il2.dso.mil/pages/viewpage.action?spaceKey=ONBOARD&title=Big+Bang+Licensing

Click here for Preview:
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/license_expectations/docs/understanding_bigbang/licensing_expectations.md

Closes:
https://jira.il2.dso.mil/browse/BBOI-732
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/458

Initial Draft Complete:
Before merging I'd like to see approval / review of the information / accuracy check from:

• A BB Customer Integration Team Member
• A member of P1 Customer Success
• BB Customer Integration Team Anchore or PM