Filebeat - Cloud Foundry Input not handling app.id and app.name correctly for access logs

[bvader]

Summary:
Filebeat : The Cloud Foundry Input and add_cloudfoundry_metadata processor are not handling / interpreting the cloudfoundry.app.id GUID correctly for the cloudfoundry.type : access

Sample Good GUID :

cloudfoundry.app.id: 4ef05e5d-d2a6-4c58-9229-d112587b74dd
cloudfoundry.app.name: cardatabase-back-end

Sample BAD GUID :
cloudfoundry.app.id: low:3046190763798940950 high:12644936126740546741

The result of this is:

1. The meta data processor fails and so the cloudfoundry.app.name is not found, cached and populated
2. Because cloudfoundry.app.name is not found and cached, the api call to get the metadata is called repeatedly for each access to the app and thus filebeat is adding significant log events to the overall log stream
3. This is potentially adding undo load to the the cloud foundry meta data API

Example Data
Discover
Index Pattern : filebeat-*
url.path : *3046190763798940950* or cloudfoundry.app.id : *3046190763798940950*'

Note both the original HTTP Accees log and the call to the Meta Data API have the malformed GUID.

Expected Result.
The GUID is properly handled,
The cloudfoundry.app.name is available and cached
There is a reduced load on the cloudfoundry API.

[elasticmachine]

Pinging @elastic/integrations-platforms (Team:Platforms)

[exekias]

@blakerouse is this fixed by #17847?

[blakerouse]

@exekias Yes it was, forgot to add it to the PR description.