Correct a minor regression in Literal Numbers: remove duplicate exercise 'g' from LiteralNumbers (Floats section)

[vivshaw]

Hello, I've noticed that PR #169 seems to have introduced a minor error in Literal Numbers: previously, the values in the Float section looked like this:

val a = 3.0
val b = 3.00
val c = 2.73
val d = 3f
val e = 3.22d
val f = 93e-9
val g = 93E-9
val h = 0.0
val i = 9.23E-9D

This version used both 93e-9 and 93E-9, to demonstrate that both are acceptable ways of representing the exponent. Furthermore, i used 9.23E-9D, to show that uppercase double literals work. But after #169, it looks like this:

val a = 3.0
val b = 3.00
val c = 2.73
val d = 3f
val e = 3.22d
val f = 93e-9
val g = 93e-9
val h = 0.0
val i = 9.23e-9d

In this version, both f and g are the same: 93e-9, and i has been swapped to lowercase. Unless I'm mistaken, this was probably not what's intended here! However, I see what caused this- looks like @juanpedromoreno was tidying up the codebase with some scalafmt magic after upgrading the version, and scalafmt stopped liking the uppercase "E" and "D". So, I would propose to fix this by setting literals.scientific and literals.double to Unchanged, allowing you to revert the Literal Numbers exercise to the prior format.

Alternatively, if you prefer to keep your .scalafmt.conf as-is, you could just remove the duplicate entry g in the Literal Numbers exercise and call it a day. If you prefer this, let me know, and I will revise my PR accordingly.

[juanpedromoreno]

Great catch, thanks for your time @vivshaw !

[juanpedromoreno]

Ooops, I've just realized that we couldn't change the .scalafmt file from here because it's automatically maintained by a CI pipeline (Github action), so it's going to be restored. Probably, removing g might be better. Thanks!

[vivshaw]

Ooops, I've just realized that we couldn't change the .scalafmt file from here because it's automatically maintained by a CI pipeline (Github action), so it's going to be restored. Probably, removing g might be better. Thanks!

Alright @juanpedromoreno, thanks for the heads up! I've rewritten this PR to remove g instead. 👍

[juanpedromoreno]

Awesome, thanks @vivshaw !