Is there a way to not create a lock file when using RestoreCommand?

[thecristidima]

This is more relevant for what I'm trying to do and way less hackish - #13363

Initial question body

I have an application that installs a NuGet package once, executes something using that package and exits. This runs in a container, so having a lock file doesn't make much sense in my case. However, I do want nuget.cache since I need to take a look at expectedPackageFiles, so I need to call CommitAsync (unless there is a way I can bypass this?).

Taking a look here, it seems one simple solution would be to just set res.LockFilePath to null before calling CommitAsync, but it feels a bit hackish (but then again, so is what I'm trying to do). Is there a better way to achieve this than doing this?

var cmd = new RestoreCommand(CreateRestoreRequest());
var res = await cmd.ExecuteAsync();
res.LockFilePath = null; // Super smart hack
await res.CommitAsync();