Description

Re-enable LogSeverity test cases after googlecloudexporter fix. Created an logging_processor-severity transformation test and renamed some test folders.

Context

• The initial issue : [googlecloudexporter] Support Google Cloud Format LogSeverity strings set as SeverityText field opentelemetry-operations-go#1030
• The fix exporter/collector: Add mapping for LogSeverity values set as SeverityText to correct SeverityNumber. opentelemetry-operations-go#1031
• Update to v0.131.0 with fix Updating opentelemetry-operations-collector #2027

Related issue

b/400435104

How has this been tested?

Checklist:

• Unit tests
  • Unit tests do not apply.
  • Unit tests have been added/modified and passed for this PR.
• Integration tests
  • Integration tests do not apply.
  • Integration tests have been added/modified and passed for this PR.
• Documentation
  • This PR introduces no user visible changes.
  • This PR introduces user visible changes and the corresponding documentation change has been made.
• Minor version bump
  • This PR introduces no new features.
  • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
  • This PR bumps the version.