Publish Component Detection to package manager registries

[JamieMagee]

Currently, all the install methods for Component Detection are to come to this repo and download the tool from the releases. I think it would be much more user friendly to publish it as a package to package manager registries.

• [ ] Windows
  • [ ] winget
• [ ] macOS
  • [ ] Homebrew
• [ ] Linux
  • [ ] RPM-based distros (Mariner, RHEL, etc.)
    • Onboarding instructions for package.microsoft.com
    • https://github.com/microsoft/CBL-Mariner
  • [ ] DEB-based distros (Debian, Ubuntu, etc.)
    • Onboarding instructions for package.microsoft.com
  • [ ] Alpine
    • https://gitlab.alpinelinux.org/alpine/aports
    • https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package
  • [ ] Arch Linux
    • https://archlinux.org/
    • https://aur.archlinux.org/
    • https://wiki.archlinux.org/title/Arch_User_Repository
  • [ ] NixOS
    • https://nixos.org/
    • https://github.com/NixOS/nixpkgs
    • Initial package in a branch
• [ ] Docker
  • [ ] Microsoft Container Registry (MCR)

The above is a bit of a brain dump of links and resources, but not exhaustive.

[melotic]

Should we modify our existing NuGet ADO release pipeline to include this packaging and distribution?

Or perhaps create a separate ADO pipeline that's hosted in this GitHub? (so we can trigger it on a release created)