Remove uses of t() in setLabel() and setDescription() calls

Tagging for coding standards and moving to the 'other' component where such issues live.

Removed t() calls from setLabel() and setDescription().

@chaitanyadessai please include an interdiff with your patches

Doing a search for ->setLabel(t(
Showed more instances from test files I don't think are related to revisions

Same for setDescription

Removed t calls.

Seems all instances have been removed. So guess we weren't testing translation of either of those. Should we open a follow up to add testing?

This still needs discussion as to whether we should actually do it, as per #14 through #18.

Thinking this through some more after working on the final t() removals in tests in 📌 Remove remaining unnecessary uses of t() in tests Active , I now think this is won't fix - we need test coverage of TranslatableMarkup passed through to various common APIs like render, form and field API and test coverage should provide good examples to use as well.

Marking "needs review" for this comment, hiding all other patches.

Explaining a bit further:

In real-world implementations of setLabel() and similar methods we use t(). By removing t() in tests we are not really testing the same way a real-world implementation would, if we only used raw strings in tests then how would be sure that the code actually works with translatable strings?

Also, tests are sometimes used as examples of features and the code is copy-pasted and then edited and used for real. If we drop t() here we risk people copy-pasting and not following the best practice of adding translatable labels and descriptions.

It's similar to when we have a test form. In most test form implementations we still wrap form element labels in t() because that's what a real world implementation of a form should do.

Explanation makes sense, anyone really disagrees please reopne.