Add support for parsing projects and solutions using Roslyn

[bstadick]

Background: For large projects and solutions that rely heavily on the use of props and targets files, a lot of context can be left out if not all project file dependencies are imported and parsed. In these cases properties may be left out or incorrectly set. Just parsing the files as xml does not fully account for these additional dependencies. Running the cyclonedx-dotnet tool on these projects can also lead to xml parsing errors when this context is left out or give incorrect results in the BOM.

Request: Add support to optionally parse project and solution files by importing them using the Roslyn build system libraries (in place of xml parsing) and to define additional build properties on the command line to better match the behavior of a dotnet build/restore command.

Additional Benefits: Adding or switching support from xml parsing to Roslyn for projects and solutions should simplify the parsing logic needed, while enhancing the parsing and overall tool's capabilities, handling edge cases, and providing nearly automatic maintainability for future changes to dotnet projects.

[github-actions[bot]]

This issue is stale because it has been open for 3 months with no activity.