Remove OM request time from Honeycomb span attributes (#3931)

# Summary

As raised in this conversation:
REDACTED

We're close to hitting the limit on unique span attributes as Honeycomb
indexes them and we generate new Org and Project IDs in every test run
where we make OM requests.

## Documentation changes

* [ ] Add an entry to [release notes](.../RELEASE_NOTES.md).
* [ ] When needed, make sure you create a new [DOCSP
ticket](https://jira.mongodb.org/projects/DOCSP) that documents your
change.

## Changes to CRDs

* [ ] Add `slaskawi`(Sebastian) and `@giohan` (George) as reviewers.
* [ ] Make sure any changes are reflected on `/public/samples`
directory.

Author: mircea-cosbuc

docker/mongodb-enterprise-tests/kubetester/omtester.py

@@ -379,7 +379,8 @@ def om_request():
                 print("failed connecting to om")
                 raise e
 
-            span.set_attribute(key=f"meko_om_request_path_{last_path_part}_time", value=time.time() - start_time)
+            # Removing OM Request time from span attributes as Honeycomb indexes unique keys and we're limited to 1000
+            # span.set_attribute(key=f"meko_om_request_path_{last_path_part}_time", value=time.time() - start_time)
 
             if response.status_code >= 300:
                 raise Exception(