Edit UI - Prevent Alteration if Not In Good Standing

## Background
This ticket came from [#6923](https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/6923), we split off the work because some of it was in the Filings UI, and some was in the Edit UI. This work is for the Edit UI(within the alteration filing itself), and **preventing users from completing an alteration filing if they are not in good standing**.

## Wireframes
(image in Figma)
https://www.figma.com/design/duipH6nvKFYQzp6uFVtWVu/Benefit-Companies--Entities-?node-id=10457-2

## Acceptance Criteria
### Scenario 1 (VERIFY)
GIVEN I want to alter to a Benefit Company
AND I am in good standing
WHEN I go to the dashboard
AND I click the Alter Now button for the first time
THEN Nothing in the alteration has been changed on my behalf (see (image in Figma)
https://www.figma.com/design/duipH6nvKFYQzp6uFVtWVu/Benefit-Companies--Entities-?node-id=10457-2

**Scenario 1 has already been achieved (we think).** Let's verify that the app doesn't automatically check change business type to BComp. Cameron thinks that it is something we did when we made the draft for the client. Let's make a draft without changing anything and see what the client sees. We want nothing to be done for them when they open it for them for the first time.

### Scenario 2
GIVEN that I have started an alteration filing
WHEN I choose to save and resume later
THEN I see a divided 'Resume' button beside my filing (not an Alter Now button)

- [ ] Save an "EDITED" flag into the draft filing
- [ ] Parse the "EDITED" flag
- [ ] "EDITED" flag dictates the text of the "Alter Now" button, show "Resume" text if EDITED flag = y
- [ ] NOT a divided resume button, just a plain resume button
- [ ] No backend validation required

### Scenario 3
GIVEN that I have an alteration filing in progress
WHEN I return to resume my filing
AND I am not in good standing
THEN I see an inactive ~divided~ 'Resume' button beside my filing
AND I see the warning text about not being in good standing

- [ ] Verify the scenarios in the table below
- [ ] Verify the "resume" button does not display "alter now" (should be implemented as part of scenario 2)


| | Button | Button secondary menu | Not in good standing warning | View and Change Company Information | Director and Address Change buttons |
| ------------------------------------- | ------------------------- | ------------------------- | ---------------------------- | ----------------------------------- | ----------------------------------- |
| Initial state - Good Standing | Alter Now Button enabled | n/a | No | enabled | disabled |
| Initial state - Not in Good Standing | Alter Now Button disabled | n/a | Yes | disabled | disabled |
| Continue state - Good Standing | Resume button enabled | Reset Company Information | No | enabled | disabled |
| Continue state - Not in Good Standing | Resume button disabled | Reset Company Information | Yes | disabled | disabled |

## Definition of Ready

- [ ] Are the Acceptance Criteria defined?
- [ ] Does the user story speak to the value being created, and is understood by the team?
- [ ] Are the dependencies known/ understood? (to the our best knowledge)
- [ ] Is this user story small enough to be completed in one Sprint?
- [ ] Dev team accepts UI artifacts? (visual UX designs ready to go)
- [ ] Is it clear whether this work is intended for deploy or limited/staged-release?