Investigate - Bad request for name check

**Describe the bug in current situation**
400 error when there's "&" in requested names.

**Link bug to the User Story**

**Impact of this bug**

**Chance of Occurring (high/medium/low/very low)**
Low

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to 'name request'
2. input name that contains "&"
3. check name
4. See error in console

**Actual/ observed behavior/ results**
400 error

**Expected behavior**
"&" and other special characters should be replaced in query string.

**Screenshots/ Visual Reference/ Source**
[Private Zenhub Image](https://api.zenhub.com/attachedFiles/eyJfcmFpbHMiOnsibWVzc2FnZSI6IkJBaHBBMkdMQVE9PSIsImV4cCI6bnVsbCwicHVyIjoiYmxvYl9pZCJ9fQ==--a5567528bcc19b897b9ec8ef6645ef2d14432995/image.png)

Start in the name request flow and reproduce the 400 error by checking a name containing "&". Trace how the check request builds its query string, then verify that special characters are handled correctly and the name check succeeds.

Written by the indexing model from the issue text.