LCFS - Changes requested

**Describe the Bug**

When an applicant re-submits a CI Application after addressing requested changes, the application status pill remains as "Changes requested" instead of resetting to "Submitted".

The status does not accurately reflect that the applicant has completed the requested updates and re-submitted the application for review.

**Expected Behaviour**

When an applicant re-submits an application after responding to requested changes, the status pill is updated from "Changes Requested" to "Submitted".

The application should re-enter the review workflow and display the appropriate status to both applicants and analysts.

**Actual Behaviour**

After the applicant re-submits the application, the status pill remains as "Changes Requested".

The status does not reflect the current state of the application.

**Implications**

Applicants and analysts may be confused about the current status of the application.

Applications that have been re-submitted may incorrectly appear to still require applicant action, making it difficult to accurately monitor workflow progress and prioritize review activities.

**Steps To Reproduce**

User/Role: BCeID Applicant

1. Submit a CI Application.
2. Have an IDIR analyst request changes to the application.
3. Observe that the application status changes to "Changes Requested".
4. Update the application and re-submit it.
5. Observe that the status pill remains as "Changes Requested".

**Expected Result**

- The application status pill changes from "Changes Requested" to "Submitted" when the application is re-submitted

Start by tracing the CI Application resubmission workflow and the status-pill display from the reproduction steps. Verify where a resubmitted application retains "Changes Requested" and confirm that completion means the status becomes "Submitted" and re-enters review.

Written by the indexing model from the issue text.