Add WriteProgress and OpenProgress methods

[halex2005]

Hi!

1. According to build-script-interaction-with-teamcity.html#reporting-build-progress, there should be support of

   ##teamcity[progressMessage '<message>']
   

   and

   ##teamcity[progressStart '<message>']
   ...some build activity...
   ##teamcity[progressFinish '<message>']
   

   service messages. This PR add this support.

2. Also I've noted that build targets somewhat obolete and I've added netstandard2.0, net6.0 and net8.0 targets.

3. I've also notices that WriteBuildProblem has required parameter named identity, bu documentation says that identity should be optional:

   identity (optional): a unique problem ID. Different problems must have different identity, same problems — same identity, 
   which should not change throughout builds if the same problem, for example, the same compilation error occurs. It must be 
   a valid Java ID up to 60 characters. If omitted, the identity is calculated based on the description text.
   

   So, I've added additional method without identity parameter to not break compatibility with existing code

Please, review this PR.

Cheers, Aleksei.

[boris-yakhno]

Hi @halex2005! Thank you for the PR, we'll take a look at it this week.

[boris-yakhno]

Could you please share the reasoning behind adding new targets? As far as I understand, netstandard1.3 should cover all the frameworks that are covered by the added targets. Maybe some targets can even be removed, as netcoreapp1.0;netcoreapp2.0;netcoreapp3.0 seem redundant here.
I'm not sure what we should do with the target frameworks and I'm interested in hearing your opinion.

[boris-yakhno]

A couple of remarks:

• Some minor grammatical changes will make the sentences sound better, e.g. "Use the method to add a progress message", "Use the method to add a progress message".
• For documentation, we should use a link to the latest version on https://www.jetbrains.com/help: https://www.jetbrains.com/help/teamcity/service-messages.html#Reporting+Build+Progress

I suggest something like this:

Suggested change

	/// <summary>
	/// <para>
	/// Use <see cref="WriteProgress"/> method to add progress message
	/// <pre>
	/// ##teamcity[progressMessage '&lt;message text>' ]
	/// </pre>
	/// </para>
	///
	/// <para>
	/// Use <see cref="OpenProgress"/> method to add progress message
	/// <pre>##teamcity[progressStart '&lt;message>']</pre>
	/// and
	/// <pre>##teamcity[progressFinish '&lt;message>']</pre>
	/// on writer dispose.
	/// </para>
	/// <para>
	/// http://confluence.jetbrains.net/display/TCD18/Build+Script+Interaction+with+TeamCity#BuildScriptInteractionwithTeamCity-ReportingMessagesForBuildLog
	/// </para>
	/// </summary>
	/// <summary>
	/// <para>
	/// Use the <see cref="WriteProgress"/> method to add a progress message:
	/// <pre>##teamcity[progressMessage '&lt;message text>' ]</pre>
	/// </para>
	///
	/// <para>
	/// Use the <see cref="OpenProgress"/> method to add a progress start message:
	/// <pre>##teamcity[progressStart '&lt;message>']</pre>
	/// and a
	/// <pre>##teamcity[progressFinish '&lt;message>']</pre>
	/// progress finish message on writer dispose.
	/// </para>
	/// <para>
	/// https://www.jetbrains.com/help/teamcity/service-messages.html#Reporting+Build+Progress
	/// </para>
	/// </summary>

[boris-yakhno]

Sorry, the documentation link in my previous comment was wrong. I have edited the comment to include the correct link.

[boris-yakhno]

How about "Writes a single progress message"?

[boris-yakhno]

How about "Writes a progress start message and returns a disposable object that writes a progress finish message on dispose"?

[boris-yakhno]

Hi @halex2005! The implementation looks good to me, I just have a question regarding the target frameworks and some minor comments on wording.