feat: add date metadata for course run assignments on coures about page

[brobro10000]

Adds course run related enrollBy date and courseStart date on the course about page for assignment based enrollments.

For instances where multiple course runs are assigned to a course, the soonest earliestExpirationDate date is displayed along with its corresponding course start date.

Properly handles tense for when a course started vs course starts.

For all changes

• Ensure adequate tests are in place (or reviewed existing tests cover changes)
• Ensure English strings are marked for translation. See documentation for more details.

Only if submitting a visual change

• Ensure to attach screenshots
• Ensure to have UX team confirm screenshots

[codecov]

Codecov Report

Attention: Patch coverage is 86.53846% with 7 lines in your changes missing coverage. Please review.

Project coverage is 88.05%. Comparing base (4f4566e) to head (5a900c2).
Report is 1 commits behind head on master.

Files	Patch %	Lines
src/components/course/data/utils.jsx	70.58%	5 Missing ⚠️
...ents/course/course-header/CourseImportantDates.jsx	94.11%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1145      +/-   ##
==========================================
- Coverage   88.06%   88.05%   -0.02%     
==========================================
  Files         393      394       +1     
  Lines        8289     8338      +49     
  Branches     2027     2047      +20     
==========================================
+ Hits         7300     7342      +42     
- Misses        947      953       +6     
- Partials       42       43       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[adamstankiewicz]

🎉

[adamstankiewicz]

[nit/curious] Is the [sortedByExpirationDate] prefix intended to match the function name? E.g., at this point in the code path sortedByExpirationDate does not exist (i.e., defined below line 928).

[adamstankiewicz]

nit: given assignments is an empty array, i'm not sure how much utility there is in including the variable itself in the logInfo?:

Would this message make sense as something like, [sortedByExpirationDate] no assignments provided in array or similar?

Semi-related (curious for your two cents!), I'm wondering if we might want to treat this and the below logInfo as logError given it seems in the code path where this function is called, it's only called when there are assigned course runs, we might want to consider it as an error that could trigger an alert for observability/monitoring. For example, if we determine there are assigned course runs, and then pass in empty array or the assignments are all missing .earliestPossibleExpiration, would we want to consider that an error? 🤔

[brobro10000]

I had this debate with myself as well when implementing this approach. I guess I overlooked the part where we are deep enough into the code path to expect assignments in the array at this point so a change to logError would make the most sense. Changing now 👍🏽
Also, at one point the function name was sortedByExpirationDate but ended up changing the name and not the variable. Updated to take that into account.