[Merge when release] Update `upgrade guide`

Import Userrequested to merge
mk/update_doc into develop

Motivation and context

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • Documentation
    • Updated upgrade guide with new section for CVAT version 2.26.0
    • Added instructions for cleaning up export cache after upgrade
    • Provided deployment-specific commands for Docker, Kubernetes, and Development environments

Merge request reports