fix: parse property types containing hyphens

[samuelmaddock]

I was testing out adding a struct property which is a string literal. When the string literal contains a hyphen, it breaks parsing.

* `prop` 'string-enum' - description

would split the type into 'string with a description of enum' - description

[MarshallOfSound]

This isn't the correct way to declare a string enum and so shouldn't be supported.

You should declare this as a string that "Can be 'foo'" with only one value

[samuelmaddock]

We have a couple places in the codebase where we type string literals

$ rg '\* `.*?` '\''' ./docs
./docs/api/structures/upload-raw-data.md
3:* `type` 'rawData' - `rawData`.

./docs/api/structures/upload-file.md
3:* `type` 'file' - `file`.

The * prop String - Can be 'foo' syntax just felt a bit awkward to write. If we feel strongly about it, I can use that though.

[MarshallOfSound]

The problem is as it stands this makes things way stricter and probably breaks something where someone forgot a space, but also this will allow people to generate invalid typescript types. E.g. Foo-Bar will be accepted but is not a valid type name

[samuelmaddock]

Works for me. Closing in favor of the "Can be" syntax for string enums.