In theory you should be able to solve this by turning off this feature of Oracle's optimizer. You would do this by running the following using sys as sysdba
sqlplus / as sysdba
ALTER SYSTEM SET "_fix_control" = '17800514:0';
ALTER SYSTEM SET OPTIMIZER_FEATURES_ENABLE= '12.1.0.2' SCOPE=BOTH;
Exit;
However, this has NOT solved the problem in any environment this has been tested on and Oracle 12.2 continues to modify these queries. An issue was opened with Oracle but they did not provide any solution.
At this time development has created a fix 3-8.3.5.3.10-ParseErrorsOracleFix--1176931-07112019.zip that works around this Oracle problem by using views. This seems to prevent Oracle from modifying the queries. This is the only known solution at this time.
(Note an earlier fix 10 solved the parse error but contained a timestamp problem. This has since been resolved by 3-8.3.5.3.10-ParseErrorsOracleFix--1176931-07112019.zip and this is being bundled up as a cleaner published fix. As long as the fix date is July 11th 2019 or later you should have the newer one).