Add Multiple Metrics About Search Performance to splunkenterprisereceiver (open-telemetry#39569)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

Added a new `splunk.search.initiation`, `splunk.search.duration`,
`splunk.search.status`, and `splunk.search.success` metrics.

<!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. -->
#### Link to tracking issue

Fixes open-telemetry#39566

<!--Describe what testing was performed and which tests were added.-->
#### Testing

Ran on a test stack and observed the metrics in Splunk Observability

![search_example](https://github.com/user-attachments/assets/746768a8-fcca-4a23-8d12-409bb7a72b51)

<!--Describe the documentation added.-->
#### Documentation

The only documentation added was the generated documentation about the
newly added metrics.

<!--Please delete paragraphs that you did not use before submitting.-->

---------

Co-authored-by: Sean Marciniak <[email protected]>

Author: 2 people

.chloggen/changes.yaml

@@ -0,0 +1,22 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: 'enhancement'
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: 'splunkenterprisereceiver'
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Added a new `splunk.search.initiation`, `splunk.search.duration`, `splunk.search.status`, and `splunk.search.success` metrics."
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [39566]
+
+# If your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# Optional: The change log or logs in which this entry should be included.
+# e.g. '[user]' or '[user, api]'
+# Include 'user' if the change is relevant to end users.
+# Include 'api' if there is a change to a library API.
+# Default: '[user]'
+change_logs: [user]