Fix behavior for escape character inputs in the Content Repository title field

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: Master
• Fix Version/s: 7.3.0 CE GA1, 7.3.10 DXP GA1, Master
• Component/s: Documents & Media
• Labels: None
• Story Points: 1
• Fix Priority: 4
• Sprint: 035 - Clefairy, 036 - Clefable
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/80453

Steps to reproduce:

1. Navigate to Repositories > Repositories
2. Add a new Repository

Scenario 1:

3. In Repository title, add

 %^& 

and publish

Expected result:
Repository %^& is added with no errors.

Actual result:
Repository %^& is added, but with a console error:

2019-10-17 03:34:16.266 ERROR [http-nio-8080-exec-9][HttpImpl:301] ^ is not a hex char

Scenario 2:

3. In Repository title, add

 %1 

and publish

Expected result:
Repository % is added with no errors.

Actual result:
Repository % is added, but with a console error:

2019-10-17 03:38:22.063 ERROR [http-nio-8080-exec-2][HttpImpl:301] Invalid URL encoding %1

Scenario 3:

3. In Repository title, add

 & 

and publish
4. Assert Content Repository Title in the control menu

Expected result:
The title reads

 & 

Actual result:

Reproduced on:
Tomcat 9.0.17 + MySQL 5.7.
Portal master 5aff3ed7a3e2cdbff9f32ebc13ac1bca99786039