chore(metrics): add metrics to identify who attempte to upgrade organization

[tianrunhe]

Description

We have a long-term bug where we lost track of the user who has performed self-serve upgrade (we just record love@parabol.co did that). This has caused issue like this one.

This small PR is a walk around fix: we emit a new metric when a user attempted to upgrade. This way later in the data sanctum we can then join this new metric with the old Organization Upgraded metric to find the match.

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog