Add AppConfig Support for MDM Managed Configurations

[ManfredWisniewski]

AppConfig Support

• AppConfigManager now exposes managed username and app-password keys alongside the server URL for reuse by dependent
• ServerSelectionActivity pre-fills the managed base URL on first launch and, after capability checks, bypasses browser login when managed credentials are present, handing them directly to account
• Declared the username and app-password restrictions in app_restrictions.xml so MDM providers can supply them via managed configuration.

🚧 TODO

• Also implement these changes for the Nextcloud App

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
  Manual Testing of the MDM support was done with Samsung KNOX Manage platform.
• 🔖 Capability is checked or not needed
• 🔙 Backport requests are created or not needed: /backport to stable-xx.x
• 📅 Milestone is set
• 🌸 PR title is meaningful (if it should be in the changelog: is it meaningful to users?)

🤖 AI (if applicable)

• The content of this PR was partly or fully generated using AI
  Changes proposed in this PR were created with the help of GPT-5-Codex.
  Building and testing the App in Android Studio was supported by Gemini.

[mahibi]

Hi @ManfredWisniewski
thank you for contributing. We will have a closer look at the Pull request soon.

[mahibi]

review is planned for next week

[ManfredWisniewski]

review is planned for next week

Thank you very much!
Sorry for not adhering to the DCO rules. I have changed my setting to always add a sign-off line to the commits in the future.
As this is really a minor change that does not (should not) interfere with any other functionalities I hope these changes can be added without this detail.

[mahibi]

Thank you very much! Sorry for not adhering to the DCO rules. I have changed my setting to always add a sign-off line to the commits in the future. As this is really a minor change that does not (should not) interfere with any other functionalities I hope these changes can be added without this detail.

Unfortunately adding the DCO is mandatory for contributions. The page https://github.com/nextcloud/talk-android/pull/6381/checks?check_run_id=84788643278 describes how the commits can be signed.
Basically it's just these 2 commands to sign your 9 commits:

• In your local branch, run:
  git rebase HEAD~9 --signoff
• Force push your changes to overwrite the branch:
  git push --force-with-lease origin AppConfig-configuration

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)