Expose Workflow Checkpoint in Workflow Reports

[assuntad23]

Part of #16556
Exposing the workflow version as workflow checkpoint on report. See comments in #16682 for reasoning.

How to test the changes?

(Select all options that apply)

• Instructions for manual testing are as follows:
  1. Create a Workflow Report
  2. Note how Workflow Checkpoint is below the Title
  3. Note: if you do not see the Checkpoint, that is because it is waiting on the store to provide it, refreshing may work. But I have it rendering conditionally, so if it doesn't return from the store in time, nothing is printed there instead.

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[nsoranzo]

@davelopez suggested to call them "revisions" instead of checkpoints, as we do in pages and toolshed, was that ruled out?

[mvdbeek]

Revision seems more official and you might expect that this is the same across servers. It doesn't matter much for pages, and for the tool shed it makes sense, but I don't think that is the case here.

[dannon]

This looks like it likely breaks basic pages? They won't have a workflow version or any of this stuff.

(actually, going to test this -- are pages also just broken in dev as-is?)

Okay, scratch that -- what breaks basic pages displaying is creating a new page with zero content and going to view it. We need to handle that part better, but it was unrelated to the changes here -- I'll follow up separately with a fix for that.

[dannon]

I think we can iterate on the styling here -- I think I'd like to see it pushed down into that blue bar subtitle bar with other attributes, but let's go ahead and move forward with this as-is.

[github-actions]

This PR was merged without a "kind/" label, please correct.

[assuntad23]

thanks @dannon!