Improve Arb function naming

[BartvHelvert]

Improves the naiming of some of the Arb functions to be more idiomatic. The following names are changed:

• bool -> boolean
• edgecase -> edgeCase
• ubyte -> uByte, ushort -> uShort etc...

Also fixes some typos in genslist.md and fixed deprecation replacements.

Closes #2305.

[sksamuel]

I can get behind the types changing, but please add deprecated forwarding methods or type aliases.
Also I don't think we should rename edgecases. We only just went through a round of deprecations and changes on the way edgecases work and I think it's ambiguous whether its one word or two anyway.

[BartvHelvert]

I can get behind the types changing, but please add deprecated forwarding methods or type aliases.

I think all of them have deprecation forward methods? The methods that don't have it didn't exist in 4.6.0 so I don't think it is worth adding deprecation warnings for those methods. If you think I missed some, let me know.

Also I don't think we should rename edgecases. We only just went through a round of deprecations and changes on the way edgecases work and I think it's ambiguous whether its one word or two anyway.

I can't find any usage of edgecase as a single word online so I don't think it is really ambiguous. But if it is to much of a breaking change I will remove it from this PR.

[sksamuel]

I can get behind the types changing, but please add deprecated forwarding methods or type aliases.

I think all of them have deprecation forward methods? The methods that don't have it didn't exist in 4.6.0 so I don't think it is worth adding deprecation warnings for those methods. If you think I missed some, let me know.

Ah ok I must have missed them first time around. I see them now.

Also I don't think we should rename edgecases. We only just went through a round of deprecations and changes on the way edgecases work and I think it's ambiguous whether its one word or two anyway.

I can't find any usage of edgecase as a single word online so I don't think it is really ambiguous. But if it is to much of a breaking change I will remove it from this PR.

Yeah you're probably right but I feel like it's one of those words in English that works both ways. Either way, I'm reluctant to change it again after we just changed it in 4.4.0. For something that most people won't use directly, I feel the benefit is low.