chore: improve spinner when used with --no-progress

[Racer159]

Description

This slightly improves the spinner to allow for interactive programs to run when --no-progress is provided.

Related Issue

Relates to #103

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Other (security config, docs update, etc)

Checklist before merging

• Test, docs, adr added or updated as needed
• Contributor Guide Steps followed

[marshall007]

Are there relevant tests I can run to reproduce the issue? Spinner has never printed cleanly for me, at least in the context of uds-cli so happy to try this out.

[marshall007]

via Slack:

The easiest way to test it is to run maru inside maru (basically build it and then call build/maru in a task) then run the parent command with and without --no-progress

This worked for me (I think) but should we add this to the e2e tests to clarify expected behavior?