Fix messy state changes on resource restart

[JamesNK]

Description

A restarted resource's state is set to Starting when an event is raised, but deleting the resource in DCP switches it back to a terminal state, e.g. Exited. Looks messy in the dashboard.

Fix is to delete the resource and then raise the resource starting event.

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

[eerhardt]

This used to get raised for ExecutableReplicaSets before. Does it still get raised with this change?

[JamesNK]

ExecutableReplicaSets is legacy code. It should be removed. But I'll do that in its own PR.