[otel] add geoip processor component

[rogercoll]

What does this PR do?

Adds the GeoIP OpenTelemetry processor into the agent. After adding the import into the internal/pkg/otel/components.go the following commands have been used to follow the project style:

$ go mod tidy; mage fmt; mage update; mage notice;

Why is it important?

It can be used in OpenTelemetry configurations, for example, in a Nginx Ingress controller integration.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

[mergify]

This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-./d./d is the label to automatically backport to the 8./d branch. /d is the digit

[mergify]

backport-v8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[kaanyalti]

@cmacknz Should we skip changelog fragments for this PR?

[cmacknz]

Didn't notice that, this should have a changelog. If EDOT collector has a separate changelog for whatever reason (I'm not aware that it does) it could go there instead, but this is a feature addition to EDOT collector so we should document it.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube