fix: allow RLS keywords (LEVEL, POLICY, SECURITY) as aliases

Added K_LEVEL, K_POLICY, and K_SECURITY tokens to RelObjectNameWithoutStart()
production to allow these keywords to be used as column aliases in addition to
table/column names. This resolves the conflict where RLS keywords were breaking
Oracle hierarchical queries and keywords-as-identifiers tests.

The fix maintains RLS functionality while allowing these keywords to work in all
SQL contexts including aliases (e.g., SELECT col AS level).

Author: AranyiRaz

src/main/jjtree/net/sf/jsqlparser/parser/JSqlParserCC.jjt

@@ -3287,6 +3287,7 @@ String RelObjectName() :
         | tk=<K_GROUP> | tk=<K_INTERVAL> | tk=<K_ON>  | tk=<K_START> | tk=<K_TOP> | tk=<K_VALUE>
         | tk=<K_VALUES> | tk=<K_CREATE> | tk=<K_TABLES> | tk=<K_CONNECT> | tk=<K_IGNORE >
         | tk=<K_QUALIFY> | tk=<K_DEFAULT>
+        | tk=<K_LEVEL> | tk=<K_POLICY> | tk=<K_SECURITY>
         )
 
     { return tk!=null ? tk.image : result; }
@@ -3296,7 +3297,8 @@ String RelObjectNameWithoutStart() :
 {    Token tk = null; String result = null; }
 {
     (result = RelObjectNameWithoutValue() | tk=<K_TOP> | tk=<K_VALUE> | tk=<K_VALUES>
-        | tk=<K_INTERVAL> )
+        | tk=<K_INTERVAL>
+        | tk=<K_LEVEL> | tk=<K_POLICY> | tk=<K_SECURITY> )
 
     { return tk!=null ? tk.image : result; }
 }