Upgrade ddtrace

[mchlwellman]

User Story - Business Need

The Datadog dependencies were intentionally left untouched during the last dependencies update (#1647). This ticket addresses the need to upgrade dd-trace and it's submodules.

• Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Notify developer
I want to upgrade Datadog dependencies
So that we minimize vulnerabilities and future upgrade pains

Additional Info and Resources

dd-trace Release Notes
Working branch is ddtrace-update
Current PR for this that failed on deploy, but passed unit tests

Breaking changes from v1 to v2.
On the branch, I followed our README documentation for updating dependencies with poetry. Passed local unit tests.

Engineering Checklist

• Upgrade the dd-trace package via poetry
• Update requirements.txt as described in README.md
• Deploy to Dev, observe that the QA Suite passes and there are no errors related to this library in the logs
• Review traces and ensure there are no issues

Acceptance Criteria

• Regression tests pass
• APM Traces are present without issues

[ldraney]

The Datadog agent image in ECR should be updated as a part of this, as it hasn't been updated since 2022!

use notification-api/.github/workflows/update-datadog-image.yaml to do so, keeping an eye out for unexpected changes.

This may have a positive impact on profiling and log digestion.

[mjones-oddball]

@mchlwellman Can you summarize what went wrong/happened when you tried to update this before? That will help whoever takes the ticket to understand the compexity/impacts.

[mjones-oddball]

Michael said the impact was for dnspython not this ticket.

[ldraney]

Kyle asked me to make a new ticket, and as I was getting informed I ended up just updating it and it passed.
I added the documentation etc to my PR

[ldraney]

Assuming it passes regression, I'll keep an eye on Datadog for a bit before asking for reviews on this.

[ldraney]

It did not pass deployment. First step will be to figure out why.

[ldraney]

Note from Kyle: updating from v1 to later version of v1 also had deployment problems, so this may be more complex for pointing