Improve workflow of applying db migration on prod

## Summary
Currently our workflow for applying db migration on prod (and deployment workflow too) need version tags as input but don't validate it (e.g. expected server tag is really server tag, not client tag and vice versa).

## [Acceptance criteria](https://www.atlassian.com/work-management/project-management/acceptance-criteria)
- [ ] validate that inputs of apply db migration on prod workflow and deployment workflow are validated as explained above.
- [ ] update deployment docs to indicate more clearly that db migrations are optional and only for backend changes. If you think that deployment docs are too complex and can be simplified and explained better you can refactor them too.

## Notes
important context

Start by finding the apply db migration on prod workflow, the deployment workflow, and the deployment docs mentioned in the issue. Check how version tag inputs are currently accepted, then add validation that server tags and client tags cannot be mixed up. Done means both workflows validate their inputs and the docs clearly say db migrations are optional and only for backend changes.

由索引模型根據 Issue 內容生成。