feat: added tracking events for password reset initiation

[sohailfatima]

INF-1379

Added a new event 'edx.user.passwordreset.initiated' which tracks the user id and the source of trigger for the password reset.

[syedsajjadkazmii]

[For my understanding] Why aren't we using segment.track?

And why is this event being introduced?

[sohailfatima]

@syedsajjadkazmii

[For my understanding] Why aren't we using segment.track?

As per my understanding, the segment.track method links each emitted event to a specific user and is preceded by the identify call which requires a user id/authentication. I believe some of the password reset cases are for users that are not logged in so this might not be possible there. For uniformity, the same method is applied on the cases where a user id might be available too. Please let me know if this is not the case and I'll review.

And why is this event being introduced?

Many learners reported that they did not receive password reset emails last month and there was barely any data available to investigate the issue at the time wrt running bulk analytics. We're aiming to add tracking to be able to deal with such cases in the future, this PR is a starting point for this effort.
Additionally, this email might be shifted to Braze in the future, so this will also help us gain an accurate idea of the volume.

[asadazam93]

Can you please update the PR description? We are not sending the email now

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.