Add support for reopened event to Vue version of contribution events

What does this MR do and why?

Related to #378677 (closed)

In &9056 we are migrating the user profile from HAML/jQuery to Vue. This is a large migration so we are splitting it up into many sections. This MR continues to build out the Activity section on the Overview tab.

There are many contribution events that we will need to support. These are documented in https://docs.gitlab.com/ee/user/profile/contributions_calendar.html#user-contribution-events. This MR adds the reopened contribution event. In future MRs I will be iteratively adding support for the other contribution event types.

Currently supported events:

• approved
• expired
• joined
• left
• pushed
• private
• merged
• created
• closed
• reopened (this MR)

Events that will be implemented in future MRs:

• updated
• commented - !128687 (merged)
• destroyed

UX note: There is currently an incorrect bottom border in the tabs. This is due to a recent change in !118597 (merged). We will be removing the tabs and moving the navigation into the new sidebar in #389842. By removing the tabs we will be able to fix this bug and because this is behind a feature flag I am going to leave it as-is for now.

Screenshots or screen recordings

Before	After

How to set up and validate locally

You don't have to do all of steps 3 - 11 to see events. Those steps are just to help understand which types of resources this MR supports.

1. Disable the super sidebar if you have it enabled. The Vue profile does not yet support it. Will be supported in #389842
2. Enable the profile_tabs_vue feature flag
   • bin/rails console
   • Feature.enable(:profile_tabs_vue)
3. Reopen an issue
4. Reopen a MR
5. Reopen a milestone
6. Reopen an Epic
7. Reopen a task
8. Reopen an incident
9. Reopen a test case
10. Reopen an Objective (see https://docs.gitlab.com/ee/user/okrs.html)
11. Reopen a key result (see https://docs.gitlab.com/ee/user/okrs.html)
12. Visit your profile

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.