There have been a number of problems trying to get the % character through translation automated bots and linter. 

See Issue 917329 and Issue 915803 and  Issue 680241 

I landed a fix to change the string to use the word `percent` instead of the % character in order to unblock the stable translation ingestion. But since this isn't correct according to the UI mocks, we need to figure out how to escape the % properly