Add e2e tests that prove we can edit an old version of a component

Overview

In 📌 Version component prop definitions for SDC and Code components Active we added support for versioned components.
There are places in the front-end code where we consult the components endpoint to get field data/json schema about a component that might need updating.
Consider a scenario where we have an old version of a component in the page - the components input form correctly renders the old version of the form (widgets etc) but the front-end might be getting json schema and hence validation rules for the current version.

Proposed resolution

Add an e2e test to validate that we can edit old versions.
If it fails, address places in the FE where we consult that list and explore how we could pass the 'point in time' validation rule for legacy versions.

User interface changes