Allow replacement of expired Name Request (post-MVP)

> _This issue was auto-created as part of the Zenhub sub-issues migration. The original entity was opened on 2024-07-02. For more details see [this post](https://changelog.zenhub.com/migration-of-epics-projects-to-sub-issues-313645?zenhub_entity_id=Z2lkOi8vcmFwdG9yL1plbmh1YkVwaWMvMjA5MDE4)._

Currently, when there is a draft IA/registration/amalgamation/restoration/continuation in filing and the NR has expired, our software (UI) blocks the draft from being resumed.

This epic is to change our software so that a draft filing with an expired NR can be resumed and the user can select a new (ie, re-submitted) NR. **This epic applies to continuation applications only.** The other filings can be updated in a future epic(s).

At a minimum, the following need to be updated:
1. The My Business Registry table currently states that the application is no longer valid. The tooltip should be updated.
2. Filings UI (entity dashboard) currently blocks the draft from being resumed. This needs to be updated.
3. Create UI (application form) currently blocks the draft from being resumed. This needs to be updated.
4. Create UI will need to identity that the current NR is expired and allow for the selection of a new NR.

NB - Renewing a NR will not affect or be affected by the above, since a NR-to-be-renewed is still valid (for a few days). The changes above are for an expired NR.

Start by tracing the My Business Registry table, Filings UI entity dashboard, and Create UI application form mentioned in the issue. Verify the continuation-only flow for a draft with an expired Name Request: it should be resumable, identify the expired request, and allow selection of a newly submitted request.

Written by the indexing model from the issue text.