Rebase openrvdas onto openrvdas_dev after v1.0.1 sync

[webbpinner]

Supersedes #17. Follow-up to the openrvdas_dev rebase tracked in the new companion issue (rebasing onto v1.0.1 instead of v1.0.0). Once openrvdas_dev has been rebased onto main v1.0.1 (https://github.com/OceanDataTools/fastapi-template/releases/tag/v1.0.1) and verified, merge/rebase openrvdas from openrvdas_dev the same way dev merges into main, per the documented branching workflow.

[webbpinner]

Note from comparing branches: openrvdas and openrvdas_dev have split by one commit each. Both are "Document project/project_dev branching model":

• openrvdas: 5af85c3
• openrvdas_dev: cbc7fe4

It's the same change committed separately on each branch. Once #22 is done, openrvdas should end up matching openrvdas_dev exactly. Drop 5af85c3 so it doesn't come back as a duplicate or conflict.

[webbpinner]

Done: openrvdas now points at the rebased openrvdas_dev (5af85c3 → 3a2887c, force-pushed). The duplicate 5af85c3 is gone.

Before pushing, I checked that the old openrvdas (5af85c3) and old openrvdas_dev (cbc7fe4) had identical files, so no content was lost. The only content openrvdas gains is main v1.0.1 plus the conflict fixes described in #22.

The two branches now point at the same commit, so future changes can go openrvdas_dev → openrvdas by PR as usual. CI lint failures are tracked in #24.