Add E2E test to verify that DevWorkspace contents are persisted during restarts #1467

Description

During pre release testing, I noticed that we were testing a scenario that can be ported to E2E tests:

• Create a Simple DevWorkspace
• Wait for it to become running
• Make changes in the project
• Update workspace to started: false
• Update workspace to started: true
• Verify that changes made before restart are persisted in DevWorkspace
• Project-clone output contains “..is already cloned…”

Acceptance Criteria

• An E2E test is added to test abovementioned scenario