Bug report: protobuf decoder is parsing strings as integers

**Describe the bug**

when decoding a proto that has a string the string is shown as integer:

**To Reproduce**

decode this string with base64:
`CloKJgokN2I5ODk3OWMtOGQ5My00M2YxLTk5NTYtZTI3NzYyMjI2YjE2EglhcHBsZV9wYXmCfSQKBDY5MzcSFUFwcGxlIFBheSBQbGFjZUhvbGRlchgJIOYPKAU=`
we can see an `apple_pay` text:
```
Z
&
$7b98979c-8d93-43f1-9956-e27762226b16 apple_pay‚}$
6937Apple Pay PlaceHolder æ(
```
but when I add protobuf decoder I'm getting:

```
{
"1": {
"1": {
"1": "7b98979c-8d93-43f1-9956-e27762226b16"
},
"2": {
"12": 8746395506356023000
},
"2000": {
"1": "6937",
"2": "Apple Pay PlaceHolder",
"3": 9,
"4": 2022,
"5": 5
}
}
}
```
the `8746395506356023000` should be `apple_pay`


Start by reproducing the supplied base64 input with CyberChef's protobuf decoder and inspect the decoder entry point found by searching for its operation name. Compare the field producing 8746395506356023000 with the expected apple_pay value; done when the sample decodes that field as text without regressing the other shown fields.

Written by the indexing model from the issue text.