⚒️🎨 Migrate user info details to Composables

[AndyScherzinger]

... style like latest expressive M3 contacts.

I'll be splitting the work on migrating to composables as a first modernization step into several UI-targeting PRs. This is the 1st.

Remark

You might spot that disabled input field that is because that field has never been editable but the former UI did not make that transparent. For the sake of dev speed I kept the logic as is. For further reference - we could also think about a filter on the adapter that is currently in place for view mode hiding items with no values in them and could extend that one for edit mode hiding elements without editing permission.

Remark2

On initial change you'll face http400 errors to to a server behavior change requesting re-authenticaiton via password confirmation which the clients doesn't do yet. This is also broken on master/older releases and I would like this PR not to be blocked by that. In order to test, first go to the web interface and change a value, after prompted for your password and submitted, you can start changing/adding fields on the client.

Remark3

There is another pre-existing bug, invalid inputs will just be rejected showing a "saving failed" while looking at the frontend which implemented actual validation blocks on the frontend level. This is missing previous to this PR, so again, I would like this PR not to be blocked by that.

🖼️ Screenshots

🏚️ Before	🏡 After

🚧 TODO

• implement editing capability (currently values are hard-reset upon editing)
• review & merge

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not needed
• 🔖 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?)

[jancborchardt]

Very nice, looks much better. Just one detail – the email address should ellipsize instead of breaking into multiple lines. Especially here with only the ".com" in the second line it looks off.

[AndyScherzinger]

Very nice, looks much better. Just one detail – the email address should ellipsize instead of breaking into multiple lines. Especially here with only the ".com" in the second line it looks off.

@jancborchardt fixed 👍 (did not update the screenshots though)

[mahibi]

when editing, the keyboard overlaps the fields address, website and "X" aka twitter (btw i absolutely agree with nextcloud/server#50841 (comment))

in the old behavior, the fields that are being edited scrolled up so they were seen above the keyboard

[github-actions]

APK file: https://www.kaminsky.me/nc-dev/android-artifacts/5931.apk



To test this change/fix you can simply download above APK file and install and test it in parallel to your existing Nextcloud app.

[github-actions]

Codacy

Lint

Type	master	PR
Warnings	99	99
Errors	0	0

SpotBugs

Category	Base	New
Bad practice	6	6
Correctness	10	10
Dodgy code	54	54
Internationalization	3	3
Malicious code vulnerability	3	3
Performance	4	4
Security	1	1
Total	81	81