Profiling NewRelic 8.11.0

[jimleroyer]

DO NOT MERGE INTO STAGING

Summary | Résumé

This adds timer and profiler around the application's initialization for capturing metrics around New Relic startup.

Related Issues | Cartes liées

• https://app.zenhub.com/workspaces/notify-planning-core-6411dfb7c95fb80014e0cab0/issues/gh/cds-snc/notification-planning-core/313

Test instructions | Instructions pour tester la modification

Deploy to the dev environment, look at the startup logs and grab the report in the application running folder named profile_report.txt.

Release Instructions | Instructions pour le déploiement

Release to the dev environment, not to staging. This will affect the workers # if merged.

Reviewer checklist | Liste de vérification du réviseur

• This PR does not break existing functionality.
• This PR does not violate GCNotify's privacy policies.
• This PR does not raise new security concerns. Refer to our GC Notify Risk Register document on our Google drive.
• This PR does not significantly alter performance.
• Additional required documentation resulting of these changes is covered (such as the README, setup instructions, a related ADR or the technical documentation).

⚠ If boxes cannot be checked off before merging the PR, they should be moved to the "Release Instructions" section with appropriate steps required to verify before release. For example, changes to celery code may require tests on staging to verify that performance has not been affected.

[jimleroyer]

Closing this pull request as this was supplanted by:

• Upgraded to New Relic v9.2.0 #2360
• Upgraded NewRelic to v10.3.0  #2367