integration: create charm using ci, view in jumble

[anotherjesse]

this builds upon #516 - adding more testing

[anotherjesse]

@jakedahn @bfollington opinions on changes in jumble to support easier testing?

[anotherjesse]

Questions:

1. I had to sleep 5 seconds on CI vs no sleep locally.

rather than having "sleep" I wonder if we can have a more accurate "wait for green sync status"

2. perhaps we should validate that we can see the changed value in the cli at the end

3. aria-label-current-foo? what is the proper aria for the charm title/content

[anotherjesse]

fixed:

1. failing tests leave chrome open!
2. re-running tests fail due to assumptions about data being empty at first - use a unique space/replica for each run

[anotherjesse]

I also want to add running common-cli to validate the cells propagated out of the web context to common memory and back to cli

[jsantell]

Looking great, thank you! Some comments on alternatives and a potential race condition

[jsantell]

Got rid of most sleeps, but seeing this error (sometimes) when clicking the button inbetween charm renders: https://jsr.io/@astral/astral/0.5.2/src/element_handle.ts#L192

TBD if waiting a bit helps, still seems ultimately intermittent