Handle NumberFormatException when parsing numbers

[jack-berg]

No description provided.

[Copilot]

Pull request overview

Improves robustness of cloud resource detection by preventing NumberFormatException from bubbling up when parsing numeric metadata/environment values in the GCP Cloud Run Job and Azure Functions resource providers.

Changes:

• Catch NumberFormatException when parsing Cloud Run Job task index and Azure Functions memory limit, skipping the numeric attribute when malformed.
• Add regression tests ensuring malformed numeric inputs do not set the corresponding attributes.
• Minor cleanup in GCPResourceProviderTest to use static Mockito imports.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
gcp-resources/src/main/java/io/opentelemetry/contrib/gcp/resource/GCPResourceProvider.java	Wrap Cloud Run Job task index parsing in try/catch and log on malformed values.
gcp-resources/src/test/java/io/opentelemetry/contrib/gcp/resource/GCPResourceProviderTest.java	Add test for malformed Cloud Run Job task index; refactor Mockito usage via static imports.
azure-resources/src/main/java/io/opentelemetry/contrib/azure/resource/AzureFunctionsResourceProvider.java	Wrap Azure Functions memory limit parsing in try/catch and log on malformed values.
azure-resources/src/test/java/io/opentelemetry/contrib/azure/resource/AzureFunctionsResourceProviderTest.java	Add test for malformed Azure Functions memory limit.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: jack-berg / name: Jack Berg (45be0c7, 4931235)