Open Source Files & Component Governance

[vaavva]

Purpose

• Adds code of conduct, notice (autogenerated and for C), security, support, and cgmanifest files
• sets up component governance pipeline
• Adds trademark information to readme

Checklist

• [x] I have read the contribution guidelines.
• I submitted this PR against the correct branch:
  • [x] This pull-request is submitted against the main branch.
  • [x] I have merged the latest main branch prior to submission and re-merged as needed after I took any feedback.
  • [x] I will squashed my changes into one with a clear description of the change when I complete the PR.

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

• ...

What to Check

Verify that the following are valid

• ...

Other Information

[vaavva]

how can we include NuGets?

@rido-min We needed to have a .sln at the root and build a project before running the detection - I added one that I just copied over from the scenarios folder, but if it should have different contents, let me know! I also get some warnings without a nuget.config, so if you can look that over as well (or let me know if there's a reason we shouldn't have it), that would be good too