2.0: Globals can't be localized

[Jack Adair]

Steps to reproduce:

1. Create a basic global

import { GlobalConfig } from "payload/types";

export const Global: GlobalConfig = {
    slug: "Test",
    label: "Test",
    fields: [
        {
            name: "name",
            type: "text",
            localized: true,
        }
    ]
}

2. Have localization enabled with more than one locale
3. Save global entry in one locale
4. Switch locales, type to change field
5. Switch back to the original locale and you will see that it is overwritten

I am able to get the desired behaviour when I disable the tenancy plugin, for this issue I'm using my blank payload template (not my working project). This only appears to be happening on globals and not collections.

Demo:

Screen.Recording.2023-11-02.at.4.40.31.PM.mov