fix(setup): hide config section if autoconfig is valid

[skjnldsv]

Fix #56160

[szaimen]

🐘

[scubamuc]

@skjnldsv confirmed

[kra-mo]

No strong opinions on whether it should be done that way in the first place, but it seems like an improvement over the status quo.

But I'd wait for any disagreements to be voiced first.

[skjnldsv]

/compile rebase

[skjnldsv]

/backport 93c72c6 to stable35

[skjnldsv]

/backport 93c72c6 to stable34

[backportbot]

The backport to stable34 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable34
git pull origin stable34

# Create the new backport branch
git checkout -b backport/56231/stable34

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 93c72c6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/56231/stable34

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable35 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable35
git pull origin stable35

# Create the new backport branch
git checkout -b backport/56231/stable35

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 93c72c6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/56231/stable35

Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress
fatal: cherry-pick failed

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[skjnldsv]

Gonna skip backports, this is for new instances anyway