Expose Upgrade Deadline Override in Publisher

With the recent change to Hide the Publish Run button for published runs (and enable the Save and Re-Publish button), we have inadvertently removed PCs ability to follow our prescribed method for updating the verified upgrade deadline date for a published run. That method was:

• Set the desired date on the draft seat “Upgrade Deadline Override” field at the bottom of the draft course run edit page in django admin

• Load the course/run in Publisher

• Click Publish Run on the affected run

As a workaround, the confluence page now instructs PCs to follow the same steps but add a trivial edit on the course to enable the Save and Re-Publish button, and click that. Not great.

So let’s just expose this override field on Seat as an available staff-only field in Publisher. Then PCs will be able to follow the following process for this fairly common case:

• Enter or edit the desired date value in this new field on the affected course run

• For Published runs:

  • Since the run will no longer be pristine, the Save and Re-Publish button will appear/enable at the Course level - clicking that takes care of set official, push to Studio, push to Ecommerce

• For all other statuses:

  • These should continue to behave as before, since the only case where we are suppressing the Publish / Update / Submit for Review button is for runs in Published status

Other notes:

• Check the status change exempt logic - I think this field should be exempt from kicking a run out of Reviewed status back to Unpublished

AC:

• Staff users can edit the Update Deadline Override associated with a course run (via its Seat) in Publisher, without needing to use django admin