Separate core `dotnetup` `record` classes

[nagilson]

Prerequisites

• I have read the dotnetup documentation.
• I have searched for existing dotnetup issues.
• I have searched for existing dotnetup discussions.

Issue type

Bug report

Description

dotnetinstall.cs contains dotnetinstall but also dotnetinstallrequest and other record types that are very useful and commonly referenced.
Each of those types should get their own file for simplicity and readability.

Often I develop in VS Code and VS Code can't properly load symbols to navigate to the types if I have not loaded the dotnetup workspace, so I try to ctrl t to the type but that also does not work unless the file name is loaded.
This will also reduce the risk of circular dependencies.

dotnetup version

No response

[dsplaisted]

My take: I don't think I really like the idea of a bunch of tiny source files for all the record types. I'm also not sure that circular dependencies are much of a problem or that this would help avoid them.

I've gotten used to having to open dotnetup.slnf in VS Code.