Add support for saving multiple frames when using animation

[noclone]

Describe your changes

Add support for saving multiple frames when using animation with --output and frame template filename

Issue ticket number and link if any

#46

Checklist for finalizing the PR

• I have performed a self-review of my code
• I have added tests for new features and bugfixes
• I have added documentation for new features
• If it is a modifying the libf3d API, I have updated bindings
• If it is a modifying the .github/workflows/versions.json, I have updated docker_timestamp

Continuous integration

Please write a comment to run CI, eg: \ci fast.
See here for more info.

[noclone]

\ci fast

[noclone]

\ci full

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.65%. Comparing base (6c5c9a0) to head (1afa9ee).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2785      +/-   ##
==========================================
+ Coverage   96.64%   96.65%   +0.01%     
==========================================
  Files         142      142              
  Lines       12918    12960      +42     
==========================================
+ Hits        12484    12526      +42     
  Misses        434      434              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Meakk]

Looks quite good! How does it behave with --animation-time?

[noclone]

Looks quite good! How does it behave with --animation-time?

I'm pretty sure it's overriden for now, so animation time is ignored. What would be the expected behavior ?

[mwestphal]

some suggestions

[mwestphal]

Definitely needs a @snoyer review

[mwestphal]

LGTM, needs a doc update and a @snoyer review :)

[mwestphal]

small doc change again

[mwestphal]

small suggestion, @snoyer please review

[mwestphal]

a test missing for full coverage

[mwestphal]

lets just for a last @snoyer review :)

[snoyer]

As mentioned in the Discord thread, I still feel like the code paths are more complex than they need to be but I haven't had time to sit down and see if they can be untangled.
Otherwise it looks like it work and the UI is good from what I can tell so we can always refactor and optimize later.

[noclone]

all suggestions applied