Remove project name parameters from pipeline templates

[mthalman]

This PR (#884) introduce a template pattern where internalProjectName and publicProjectName parameters were defined and passed around to templates rather than hardcoding the actual AzDO project names:

docker-tools/eng/common/templates/stages/build-test-publish-repo.yml

Lines 22 to 23 in 86df1f6

	internalProjectName: null
	publicProjectName: null

This pattern doesn't provide much value. In fact, it has negative value because developers need to ensure that these values get passed around through the template graph. Omitting this can lead to unintended behavior. We should consider removing these parameters and simply hardcoding the project names where they are needed.

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[lbussell]

[Triage] This is something we can work on incrementally - as we make changes to existing pipelines we should feel free to replace these variables where appropriate.