Do not escape org name twice

[eaon]

Description of Changes

If InstanceConfig.organization_name is escaped before writing it to the database, we'd need to mark every use of it in the templates as | safe, which is more dubious than not escaping the database entry in the first place.

Fixes #6357

Testing

• Log into JI with an admin user
• Navigate to the Instance Configuration interface

• Change the instance name to something that would be escaped (for example &s or ümläüts) and click Set Organization Name
• When you get the Preferences saved. notification, none of the characters of the name you submitted are double-escaped
• Navigate to the SI and verify the correct name is shown in the title

Checklist

• I have written a test plan and validated it for this PR
• These changes do not require documentation

[zenmonkeykstop]

Test plan checks out, made a couple of attempts to try SQL injections which were shrugged off by SQLAlchemy without fuss!