Fix URL handling regression

[rtibbles]

Summary

#12028 introduced a regression due to a copy paste error by me, that tried to use query_params inside a POST request.
Reverts back to data.

References

Fixes #12048

Reviewer guidance

Start with a fresh KOLIBRI_HOME
Use the On My Own workflow
Create a user whose username already exists on a remote facility
Complete setup
Go to user profile
Change Learning Facility
Go through the steps to merge your user with the existing user
Rejoice when it works.

---

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.16.1b1.dev0_git.3.g26fae0da.pex
Windows Installer (EXE)	kolibri-0.16.1b1.dev0+git.3.g26fae0da-unsigned.exe
Debian Package	kolibri_0.16.1b1.dev0+git.3.g26fae0da-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.1b1.dev0+git.3.g26fae0da-0.4.0.dmg
Android Package (APK)	kolibri-0.16.1b1.dev0+git.3.g26fae0da-0.1.1-debug.apk
TAR file	kolibri-0.16.1b1.dev0+git.3.g26fae0da.tar.gz
WHL file	kolibri-0.16.1b1.dev0+git.3.g26fae0da-py2.py3-none-any.whl

[marcellamaki]

Thanks, Richard - this looks like the right fix. I'm going to merge and include in a beta2 for Peter's review tomorrow

[pcenov]

I confirm - the issue described in #12048 is fixed now.