Standardize all "Prints" comments in documentation

[Mickeon]

Related to

• Fix C# boolean "Prints" comments in documentation #99089
• Update documentation's "Prints" comments after #47502 #99081

This PR tries to standardize the common # Prints comment present in a lot of the class reference. This is based off of a few rules, which are taken from my own written attempt to "explain myself":

• Where appropriate, use the following common inline comments:
  • # Prints {value}: After a print call. (or similar).
    Suitable for beginner topics, where you want the user to see the result upon copying and pasting the code sample. {value} should be formatted exactly how it would be printed to the console. No trailing period.
    • Do not encompass in quotes, unless a single String/StringName is the argument for print.
    • Encompass everything in quotes, when multiple arguments in the same print are used.
    • Beware of C# differences. GD.Print() outputs "True" and "False", trims the trailing .0, and outputs enum constants' names instead of their value.

This PR is still a draft because these rules are still not consistent.

---

As of writing this, not many additional changes are done to the affected descriptions.
Note that, in the grand scheme of things, this is an extremely minor change. Approve and merge this PR only if you feel like this is worth the localization needing to be refreshed.

[Repiteo]

Given the mentioned PRs fall under a similar umbrella, and this is already a niche change, I'd recommend consolidating all of them into this PR

[Mickeon]

Out of these kinds of PRs I decided to keep #99081 separate because the future of #47502 is still a bit murky. Not sure it should be merged into once batch but I can do it just fine.

[tetrapod00]

The changes to prints do seem to match the standards laid out in the OP. The other improvements made along the way generally look okay to me.

[akien-mga]

Looking at this example specifically, I wonder if a policy that is to use quotes for strings but not for number types is the right one.

What gets printed is:

ab[1, 2, 3]

which doesn't differ much from the output of print(42) or print("ab[1, 2, 3]").

var a = [1, 2, 3]
print("a", "b", a)
print("ab[1, 2, 3]")
print(42)

prints:

ab[1, 2, 3]
ab[1, 2, 3]
42

So maybe we should use quotes all the time and not just for strings?

[Mickeon]

I'll leave that up for you or someone else to decide. Doing this is bikeshedding a bit and would be a whole lot more lines to change, but I do not mind doing it so long as it's consistent.