Improve field label from key heuristics

[gwyneplaine]

Description

Field labels were previously using inflection to coerce the field key into a human readable label.
This caused incongruity with acronyms in particular. To address this we've done the following:

• Remove inflection from the fields package
• Moved the core logic in the keyToLabel utility in @keystone-next/keystone-legacy to @keystone-next/utils-legacy
• Made minor adjustments to the logic. **
• Replace the invocation of inflection in the fields implementation with the new humanize utility.

**The previous logic in keyToLabel would turn the following string standardHTMLThing to Standard HTMLThing
This is not consistent with the asserted behaviour, we've augmented this logic now to ensure the transformation is as follows:
standardHTMLThing --> Standard HTML Thing

Before:

After:

I'm not really sure if this should be considered a breaking change or not, as I'm unclear if the label also affects non ui specific operations. (for example the returned value of keyToLabel is used both in pluralize and singularize in the list implementation)
perhaps @timleslie or @mitchellhamilton may have a semver suggestion here.

----- Edit ------
Removing the logic changes to keyToLabel / humanize, as this would be a major breaking change.
The field label logic should still be a drastic improvement from before.

[changeset-bot]

🦋 Changeset detected

Latest commit: e561094

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@keystone-next/fields	Patch
@keystone-next/utils-legacy	Minor
@keystone-next/keystone-legacy	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/9j7YxUBNR6jWWcgCPN3qf5VEndXE
✅ Preview: https://keystone-next-docs-git-key-354-improve-heuristics-keystonejs.vercel.app

[emmatown]

Yeah, this is a major because the label for lists that comes from keyToLabel is then passed through pluralize and then some more things happen to it and it ends up in the GraphQL API.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e561094:

Sandbox	Source
@keystone-next/example-sandbox	Configuration

[gwyneplaine]

Yeah, this is a major because the label for lists that comes from keyToLabel is then passed through pluralize and then some more things happen to it and it ends up in the GraphQL API.

@mitchellhamilton mm, releasing a major for a slightly more correct label utility seems bad to me.
I'll revert the logical changes made for this, and it should still satisfy the field bug correction.

At which point we can probably release this as a patch, provided the label in the packages/fields/src/Implementation.js is isolated to just UI concerns. 🤞

[emmatown]

Needs a changeset

[timleslie]

LGTM 👍