fix: recalculate grid span count after rotation

[himu-gupta]

Summary

• Recalculate the file-list grid span count after configuration changes.
• Keep the fragment's selected view type in sync when toggling between list and grid.
• Invalidate staggered-grid span assignments and request a relayout after the mode/orientation update.
• Add an unreleased changelog entry.

Fixes #4884

Verification

• JAVA_HOME="/Applications/Android Studio.app/Contents/jbr/Contents/Home" ANDROID_HOME="/Users/himu/Library/Android/sdk" ./gradlew --no-daemon --console=plain :owncloudApp:compileOriginalDebugKotlin
• git diff --check

[CLAassistant]

All committers have signed the CLA.

[joragua]

Hi @himu-gupta! Thanks for opening this PR! 🙌🏻

Some improvements here before the CR:

1. Do not to forget to use Conventional commits for the message
2. Commits must be GPG/PGP signed, and it'd be great if each commit include a Signed-off-by line
3. I'd separate the calens into a different commit with the message: chore: add calens file

Let us know if you have any doubts and we will help you! I will start with the code review when all changes are done 🍻

[himu-gupta]

Hi @himu-gupta! Thanks for opening this PR! 🙌🏻

Some improvements here before the CR:

1. Do not to forget to use Conventional commits for the message
2. Commits must be GPG/PGP signed, and it'd be great if each commit include a Signed-off-by line
3. I'd separate the calens into a different commit with the message: chore: add calens file

Let us know if you have any doubts and we will help you! I will start with the code review when all changes are done 🍻

Thanks @joragua, I have done the requested changes.

[jesmrec]

Thanks for your contribution @himu-gupta!! Let me tell you how the process is. Basically, there are two phases after the PR is correct (signed commits, separated changelog, conventional commits correct...):

1. Code review: team will review the code you pushed and make suggestions for improvement. Usually, @joragua takes care of it.

2. QA: Once code review is approved, the feature/fix will be tested to detect defects or unexpected behaviors. I will take care of that.

For sure, all CI checks must be green as well, otherwise merging will be blocked.

Code review will start soon, keep tuned!!

[himu-gupta]

Thanks for your contribution @himu-gupta!! Let me tell you how the process is. Basically, there are two phases after the PR is correct (signed commits, separated changelog, conventional commits correct...):

1. Code review: team will review the code you pushed and make suggestions for improvement. Usually, @joragua takes care of it.
2. QA: Once code review is approved, the feature/fix will be tested to detect defects or unexpected behaviors. I will take care of that.

For sure, all CI checks must be green as well, otherwise merging will be blocked.

Code review will start soon, keep tuned!!

Thanks for the insight