Corrected default output directory for dotnet publish

[svick]

Fixes #5309.

To verify this is indeed the behavior of dotnet publish, I looked at the source code (cli, sdk) and also tried running the command myself.

[dasMulli]

If we want to be super-correct the ./ beginning may be misleading as the path is relative to the project and the ./ part in docs may trick readers into thinking it was relative to the command.
(I'm still hoping to fix that for a 3.0 SDK since the breaking change was too late for 2.0 - dotnet/cli#7166).

Does that make sense or is it too overthinking?

[svick]

@dasMulli Instead of trying to take attention away from the fact that the default path is relative, maybe it would make more sense to make it clearer that the following sentence applies to the default path too?

If a relative path is provided, the output directory generated is relative to the project file location, not to the current working directory.

I'm not sure what would be a good wording for that. Maybe removing the "provided" part would be enough?

If the path is relative, the output directory generated is relative to the project file location, not to the current working directory.

[BillWagner]

Thanks for making this change @svick

I've reviewed the changes, and the CLI source in your comment, and I'll now.

Thanks again for your contribution, and thanks @dasMulli for adding his review.

[Mike-E-angelo]

Cooooool... so there was something going on here. Thank you all for your impressive efforts! It's really exciting to see everything work together and to even be a part of it. 👍