Review diagnostic messages for missing single quotes around symbol names

[Evangelink]

Fix #1714

I did a first review of all the diagnostic messages to find missing quotes. I have deliberately skipped all description messages (let me know if you want me to update them).

I have, for now, only changed the resource files and when we agree upon the texts I'll update the various translation files.

Doing this review of the messages, I have a couple of remarks to make:

• There is no consistency on whether title and messages shall end (or not) with a period.

• Some of the messages are using a pascal case rule for all the words of the message, this probably reads weird when we happen to have the issue raised.

• There is no consistency on how attributes are referred to. We can find Use [XXX], Use [XXXAttribute], Add XXX attribute or Add XXXAttribute. It might be good to always use the same style.

[mavasani]

There is no consistency on whether title and messages shall end (or not) with a period.

@sharwell do we have any precedence on this?

[mavasani]

There is no consistency on how attributes are referred to.

I'd say lets just choose one style and be consistent. I am fine with using Add 'XXXAttribute'.

[mavasani]

Suggested change

	<value>Propagate 'CancellationTokens' When Possible</value>
	<value>Propagate 'CancellationToken' when possible</value>

[Evangelink]

That's one example of

Some of the messages are using a pascal case rule for all the words of the message

[mavasani]

Suggested change

	<value>Propagate 'CancellationTokens' When Possible</value>
	<value>Propagate 'CancellationToken' when possible</value>

[sharwell]

💭 Another option here is:

Suggested change

	<value>Apply 'DiagnosticAnalyzer' attribute for '{0}'.</value>
	<value>Apply [DiagnosticAnalyzer] for '{0}'.</value>

[Evangelink]

I was thinking about this syntax first but then I thought that was too C# oriented (thinking about vb.net devs). Let me know if you still prefer to go for the brackets.

[sharwell]

There is no consistency on whether title and messages shall end (or not) with a period.

My preference is:

1. No '.' for single-sentence titles and messages (and avoid multi-sentence unless it substantially detracts from clarity)
2. Use full sentences with '.' for descriptions

[sharwell]

There is no consistency on how attributes are referred to.

My preference is 'SomeAttribute' for diagnostics, and [Some] for code fixes.

[Evangelink]

I will create a ticket and list what was said in this PR, close this PR and open a new one with only the changes we agreed upon.