Replacing string localization message id data fields with the new LocId type

[DrSmugleaf]

LocId has been added as a type, which should be used in data fields that hold localization message ids (space-wizards/RobustToolbox#4456)
For example:

    /// <summary>
    /// Locale id for the pick verb text.
    /// </summary>
    [DataField, ViewVariables(VVAccess.ReadWrite)]
    public string VerbText = "comp-pick-random-verb-text";

    /// <summary>
    /// Locale id for the empty storage message.
    /// </summary>
    [DataField, ViewVariables(VVAccess.ReadWrite)]
    public string EmptyText = "comp-pick-random-empty";

Becomes:

    /// <summary>
    /// Locale id for the pick verb text.
    /// </summary>
    [DataField, ViewVariables(VVAccess.ReadWrite)]
    public LocId VerbText = "comp-pick-random-verb-text";

    /// <summary>
    /// Locale id for the empty storage message.
    /// </summary>
    [DataField, ViewVariables(VVAccess.ReadWrite)]
    public LocId EmptyText = "comp-pick-random-empty";

The values for these fields in both prototypes and code will then be automatically validated by the yaml linter, to check if they exist in any .ftl files under Resources/Locale.

Where LocId is used, running the yaml linter may also be used by downstreams of a different language to check for missing localization ids used by prototypes in their locale, if the fallback culture is not set to English.

New PRs must start using LocId where relevant, in the same way as ProtoId and EntProtoId. (#20586)