fix: keys split into 2 strings, which allows # in fullName

[mshanemc]

What does this PR do?

allow # in fullNames for components

What issues does this PR fix or reference?

#, @@
@W-5185915@

Functionality Before

For a component with # in its name (see example on the WI), SDR would call string.split('#') and get confused. When trying to pull, it wouldn't be able to find matching metadata

Functionality After

finds metadata (has to split into two strings on the first instance of the delimiter)

[WillieRuemmele]

let's hope there's never a metadata type with # in it

[mshanemc]

let's hope there's never a metadata type with # in it

Custom#Labels

[WillieRuemmele]

QA'd and it's possible to have # in metadata names, but it is also possible to have too many # in metadata names, and after encoding from # to %23 will blow past Node's limit for file names causing an ENAMETOOLONG error