wip: show how to create rules_license PackageInfo

[alexeagle]

---

Type of change

• Bug fix (change which fixes an issue)
• New feature or functionality (change which adds functionality)
• Style (white-space, formatting, etc...)
• Refactor (a code change that neither fixes a bug or adds a new feature)
• Performance (a code change that improves performance)
• Documentation (updates to documentation or READMEs)
• Chore (any other change that doesn't affect source or test files, such as configuration)

For changes visible to end-users

• Breaking change (this change will force users to change their own code or config)
• Relevant documentation has been updated
• Suggested release notes are provided below:

Test plan

• Covered by existing test cases
• New test cases added
• Manual testing; please provide instructions so we can reproduce:

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Alex Eagle seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}