feat(stdlib)!: Add an Ascii submodule to Char and move isAscii, toUppercase, toLowercase

[spotandjake]

This pr adds some additional Ascii helper functions to the Char module, it also moves the existing Ascii utilities into a new Ascii submodule within Char.

Breaking: This is a breaking change as isAscii, toAsciiLowercase, toAsciiUppercase, isAsciiDigit and isAsciiAlpha were all moved and renamed within the submodule.

[ospencer]

I'm in favor of an Ascii submodule.

[spotandjake]

I'm in favor of an Ascii submodule.

Done

[ospencer]

This is awesome. Really looking forward to this.

[ospencer]

I think it's fine to do the examples as just Ascii. without the leading Char..

[spotandjake]

I think we should keep the Char.Ascii.isAscii, I feel like it's not very long and it makes the examples runnable, in other modules such as array I was using the pattern:

use Array.{ module Immutable }
assert Immutable.isEmpty(Immutable.empty) == true

but I felt that the module name ascii was small enough here to just directly inline it. I think there is real value in having our examples be as runnable as possible while still being small.

[ospencer]

Shouldn't these be chars? If someone really needs the code then they can do a Char.code on it.

[spotandjake]

We currently use the code on the top level module Char.min. I think if we really want to change that we should do it in a seperate pr after this. Though there is the argument here that min and max are odd values for chars whereas they make more sense in relation to charCodes. maybe we have both minCode, maxCode and min, max?