Check status of TextBuffer Unit Tests in CI

[miniksa]

If the TextBuffer unit tests aren't named .Unit.Tests. then I'm pretty sure the CI isn't running them.

Originally posted by @miniksa in #843

[metathinker]

Unfortunately, you are right. I looked at test results for my PR here:
https://dev.azure.com/ms/Terminal/_build/results?buildId=15717&view=ms.vss-test-web.build-test-results-tab

• Searching for "defaultcolor" should find TextBuffer.UnitTests.dll!TextColorTests::TestDefaultColor , but in fact matches nothing.
• Searching for "boxarea" should find Terminal.Core.Unit.Tests.dll!TerminalCoreUnitTests::SelectionTest::SelectBoxArea , and it does.

[DHowett-MSFT]

So, question. Is it better to change this:

terminal/build/pipelines/templates/build-console-steps.yml

Lines 52 to 54 in fd98145

	testAssemblyVer2: |
	$(BUILD.SOURCESDIRECTORY)\**\*unit.test*.dll
	!**\obj\**

or to change this:

terminal/src/buffer/out/ut_textbuffer/TextBuffer.Unittests.vcxproj

Line 25 in fd98145

<TargetName>TextBuffer.UnitTests</TargetName>

?

[miniksa]

So, question. Is it better to change this:

terminal/build/pipelines/templates/build-console-steps.yml

Lines 52 to 54 in fd98145

	testAssemblyVer2: |
	$(BUILD.SOURCESDIRECTORY)\**\*unit.test*.dll
	!**\obj\**

or to change this:

terminal/src/buffer/out/ut_textbuffer/TextBuffer.Unittests.vcxproj

Line 25 in fd98145

<TargetName>TextBuffer.UnitTests</TargetName>

?

The latter, @DHowett-MSFT, is what I want to do. I commented on your PR #913 earlier that we should make this consistent across all testing projects. And the latter works toward consistency.