Challenge/Lab/Workshop Code Saving Consistency, UX

### Describe the Issue

A recent [question on Reddit](https://www.reddit.com/r/FreeCodeCamp/s/qL9DT67QAv) about not being able to see their prior solutions. I had bad information about what was saved and under what circumstances.

In asking on the Discord chat it was pretty clear that not even the mods know what is saved and what is not.

It sounds like some stuff is saved until submitted, which is kinda messed up.

### Affected Page

N/A

### Steps to Reproduce

N/A

### Expected behavior

I think there is a general expectation with this sort of editor that stuff will be saved. Even if it's only saved in local storage, that seems better than nothing.

I know there have been problems with user code causing infinite loops, so that needs to be dealt with.

I think the minimum is that there needs to be clear, user facing feedback about what is and is not saved, and under what circumstances it might be deleted.

Additionally, these rules should probably be consistent across all challenge types, as long as it's technically feasible.

### Screenshots

_No response_

### System

N/A

### Additional context

_No response_