UI - Update alteration and existing correction to use new resolution date format

- [ ] Alteration
- [ ] Use new schema while submitting to api
- [ ] Existing correction
- [ ] Use new schema while submitting to api
- [ ] Include all existing resolution dates (same as new correction)

- ref schema for new format https://github.com/bcgov/business-schemas/blob/main/src/registry_schemas/schemas/share_structure.json#L103

Old format: `["2026-09-10"]`
New format: `[{"date": "2026-09-10"}]`

In correction when resolution date already exist and adding new one:
```
[
{"id": , "date": "2020-01-05"}, -- existing
{"date": "2026-09-10"} -- new
]

```

Start with the UI submission paths for Alteration and Existing correction, then compare their payloads with the linked share_structure.json schema. Confirm that new and existing resolution dates use objects, preserve existing IDs during correction, and include all existing dates before considering the work done.

Written by the indexing model from the issue text.