Add monitoring agent logs to diagnostics (#4130)

# Summary

Dumps monitoring agent logs:
- monitoring-agent-verbose.log
- monitoring-agent.log
- mongodb-agent-monitoring stdout as it contains different logs

## Proof of Work

![Screenshot 2025-02-26 at 12 46
21](https://github.com/user-attachments/assets/3cfe8f61-f13d-4945-ba0c-78f6f3183535)

Monitoring files for:
-
[kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-stdout.log](https://operator-e2e-artifacts.s3.amazonaws.com/logs/ops_manager_kubernetes_e2e_multi_cluster_om_appdb_e2e_om_appdb_monitoring_tls_patch_0cf57be68d401429bfad2dd3867b26bda4ee9cc2_67beec335588f90007261179_25_02_26_10_25_56/0/kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-stdout.log)
-
[kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-verbose.log](https://operator-e2e-artifacts.s3.amazonaws.com/logs/ops_manager_kubernetes_e2e_multi_cluster_om_appdb_e2e_om_appdb_monitoring_tls_patch_0cf57be68d401429bfad2dd3867b26bda4ee9cc2_67beec335588f90007261179_25_02_26_10_25_56/0/kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent-verbose.log)
-
[kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent.log](https://operator-e2e-artifacts.s3.amazonaws.com/logs/ops_manager_kubernetes_e2e_multi_cluster_om_appdb_e2e_om_appdb_monitoring_tls_patch_0cf57be68d401429bfad2dd3867b26bda4ee9cc2_67beec335588f90007261179_25_02_26_10_25_56/0/kind-e2e-cluster-2_om-tls-monitored-appdb-db-0-0-monitoring-agent.log)

## Checklist
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you checked for release_note changes?

## Reminder (Please remove this when merging)
- Please try to Approve or Reject Changes the PR, keep PRs in review as
short as possible
- Our Short Guide for PRs:
[Link](https://docs.google.com/document/d/1T93KUtdvONq43vfTfUt8l92uo4e4SEEvFbIEKOxGr44/edit?tab=t.0)
- Remember the following Communication Standards - use comment prefixes
for clarity:
  * **blocking**: Must be addressed before approval.
  * **follow-up**: Can be addressed in a later PR or ticket.
  * **q**: Clarifying question.
  * **nit**: Non-blocking suggestions.
  * **note**: Side-note, non-actionable. Example: Praise
  * --> no prefix is considered a question

Author: MaciejKaras

scripts/evergreen/e2e/dump_diagnostic_information.sh

@@ -89,6 +89,9 @@ dump_pod_logs() {
         echo "Writing agent and mongodb logs for pod ${pod} to logs"
         kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/automation-agent-verbose.log" "logs/${prefix}${pod}-agent-verbose.log" &> /dev/null
         tail -n 500 "logs/${pod}-agent-verbose.log" > "logs/${prefix}${pod}-agent.log" || true
+        kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/monitoring-agent-verbose.log" "logs/${prefix}${pod}-monitoring-agent-verbose.log" &> /dev/null
+        kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/monitoring-agent.log" "logs/${prefix}${pod}-monitoring-agent.log" &> /dev/null
+        kubectl logs -n "${namespace}" "${pod}" -c "mongodb-agent-monitoring" > "logs/${prefix}${pod}-monitoring-agent-stdout.log" || true
         kubectl cp "${namespace}/${pod}:var/log/mongodb-mms-automation/mongodb.log" "logs/${prefix}${pod}-mongodb.log" &> /dev/null || true
         # note that this file may get empty if the logs have already grew too much - seems it's better to have it explicitly empty then just omit
         kubectl logs -n "${namespace}" "${pod}" | jq -c -r 'select( .logType == "agent-launcher-script") | .contents' 2> /dev/null > "logs/${prefix}${pod}-launcher.log"