Add a Local Nuget Server That uses Self Signed certificate

[Nigusu-Allehu]

Fixes: https://github.com/NuGet/Client.Engineering/issues/2796
This PR adds a V3 Local NuGet Server that uses a self signed certificate

• The server will only have a package named abcdefghijkl
• And upon restore it would act like a regular NuGet server and provide the client with abcdefghijkl.1.0.0.nupkg
• However it uses a self signed certificate which should block https connections as it would be invalid for the client
• The source value of this server is https://127.0.0.1:44444/v3/index.json
• This will be used for manula testing disableTLSCertificateValidation

[zivkan]

Perhaps for the vendors manual testing this PR's solution might be easier, but also consider pre-existing options which might have had less development cost:

• Use Sleet and host on any web server that can support TLS (for example dotnet-serve with the -S argument)
• Use another self-hosting Nuget server like Bagetter, potentially with a dev-cert

[Nigusu-Allehu]

Perhaps for the vendors manual testing this PR's solution might be easier, but also consider pre-existing options which might have had less development cost:

• Use Sleet and host on any web server that can support TLS (for example dotnet-serve with the -S argument)
• Use another self-hosting Nuget server like Bagetter, potentially with a dev-cert

Thanks! These suggestions would have definitely made my life easier. I didn't know we could just generate a NuGet feed just like that. I'll be sure to consider them for future projects.