Create common components to represent dashboard activity pages

[acelaya]

Depends on #6285

Create a common OrderableActivityTable component to render activity tables in the dashboard pages. This allows to:

1. Test the table ordering logic only once.
2. Have a consistent structure and look-and-feel between sections.

Additionally, this PR makes these other changes:

1. Render titles using CardHeader + CardTitle instead of a h2 inside the CardContent itself. This title will potentially be removed replaced by a breadcrumb, but that requires a bit of experimentation.
2. Make all columns in the table but the first one be sorted in descending order by default, thanks to the implementation from Allow to provide initial order per DataTable column frontend-shared#1564

[robertknight]

This generally looks good. Just some minor comments.

[robertknight]

Unrelated to the changes in this PR, when transitioning from a course to an assignment, we already know the assignment title so we could use that as the initial value until we get the "latest" value back from the API.

[acelaya]

Yep, we should do that.

I have been lately thinking on how we can better handle transitions between routes, and then combine that with a global loading state/splash screen for the initial load. I'll be creating some POC soon.

[robertknight]

What is the typeof for here?

[acelaya]

columnName has type keyof T, which translates into string | number | symbol.

Without the check for string type, TypeScript complains when passed to Array<string>.includes().

This is related to the discussion here https://hypothes-is.slack.com/archives/C1M8NH76X/p1716819580379869, but I skipped this part from the conversation because it was easy to solve.

[robertknight]

LGTM. Just a couple of notes about comments.