fix: border type enums as strings

[jimniels]

The old file schema used integers as enums for border types whereas the new schema introduced here uses human readable strings.

This results in old files with special borders having integers as values (instead of strings) and therefore not passing zod parsing

For example, the new file formats look like this:

"borders": [
  {
    "x": 5,
    "y": 6,
    "vertical": {
      "type": "dashed"
    }
  }
]

Whereas the previous file format was:

"borders": [
  {
    "x": 5,
    "y": 6,
    "vertical": {
      "type": 4
    }
  }
]

• Update the v1 schema to reflect the old enums and add v1_1 to use the new strings method, with the updater function updating old values - WILL DO THIS IN ANOTHER PR
• Add tests to denote this change

[aws-amplify-us-west-2]

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-400.de5w5iglj13on.amplifyapp.com