[Feature request]: ase Trajectory logging to standard output

[laserkelvin]

Feature/behavior summary

Would be convenient to write a custom class for outputting the state of a trajectory to standard output.

Request attributes

• Would this be a refactor of existing code?
• Does this proposal require new package dependencies?
• Would this change break backwards compatibility?
• Does this proposal include a new model?
• Does this proposal include a new dataset?
• Does this proposal include a new task/workflow?

Related issues

One of Carmelo's points raised in #215 review.

Solution description

I believe the trajectory writer should take arbitrary streams to write to, in which case we could potentially just use standard output like any other stream, and add some lip gloss to make it pretty.

Additional notes

No response