New pack formats do not conform to standard versioning conventions

While the change to major/minor versions for data and resourcepacks is appreciated, requiring that max_format and min_format be specified as a list of two int is extremely counterintuitive and in opposition to how every other versioning system that I’m aware of handles semantic versioning, which is simply to require that the value be specified (or, better, interpreted) as a string.

That is, I would expect the following entries in pack.mcmeta to be valid:

{
  "pack": {
    "min_format": 65.2,
    "max_format": "66.11"
  }
}

I also question whether it was really necessary to break backwards compatibility by dropping support for supported_formats