Wow, interested to know how does it look like for companies & individual in 2025?
Would I remain one of us 
, if I dare to say: I have never throughly used or feel like using any test case management tool, not that they are not useful, they absolutely are for some business, by chance I haven’t had an opportunity to use them professionally. Even though I know each one of them out there in the market.
I have been associated with large organisation & startup as well. I have had used: Asana, Redmine, Jira’s built-in feature called: “Smart Check list” & couple of others - I might be old school in that sense that I still keep all the test cases that are there in the eco system to shared Excel file. 
because - why not?
So, how do we manage them? How do we know whats needed to be tested and how can I guide? Answer: a defined steps for a story thats whats needed.
Stories are easy target to breakdown test cases, because it will be divided further into subtasks for specialists i-e: BE/FE/DB/Services etc.
- Engaging QAs early, shift left.
- Declare the test cases there and then under the story. (Spend a good time with developer 30min to 1h) I call it - QA-Kickoff.
- When the work starts on that story, make sure those test cases have been covered , tested later on , engage in code reviews.
- Make sure results are shared as Testing notes. either by this plug in - or in simply text based jira field called: Testing Notes. Simple and easy.
And time to time I do visit the test cases to update/edit as they are part of entire test strategy not just one feature and everyone refers to them when needed but in reality the test cases written under stories are suffice and targeted.
Its the ‘Quality process model’ I had proposed and we follow. I believe it must be different with different team structure, thats the beauty of Agile, choose what works best for you! 