Modified getLogString with more NULL Safety

The old implementation causes a NPE if the `session` or the `project` is null in line 1102.  This new implementation of will not.

The session being NULL is plausible, because the `appendLogParameters` function, which is called in line 1111, starts with a NULL check.

foundation/org.eclipse.persistence.core/src/main/java/org/eclipse/persistence/queries/StoredProcedureCall.java

@@ -1099,7 +1099,7 @@ public String getLogString(Accessor accessor) {
                     session = getQuery().getSession();
                 }
                 List<String> procedureArgs = getProcedureArgumentNames();
-                boolean indexBased = procedureArgs.size() == 0 || procedureArgs.get(0) == null || session.getProject().namingIntoIndexed();
+                boolean indexBased = isIndexBased(procedureArgs, session);
                 Collection<String> parameters = new ArrayList<>();
                 for (int index = 0; index < getParameters().size(); index++) {
                     if (indexBased) {
@@ -1115,4 +1115,13 @@ public String getLogString(Accessor accessor) {
             return getSQLString();
         }
     }
+
+	private boolean isIndexBased(List<String> procedureArgs, AbstractSession session) {
+    	boolean hasNoArgs = procedureArgs.size() == 0 || procedureArgs.get(0) == null;
+    	boolean isNamingIntoIndexed = false;
+    	if (session != null && session.getProject() != null) {
+    		isNamingIntoIndexed = session.getProject().namingIntoIndexed();
+    	}
+    	return hasNoArgs || isNamingIntoIndexed;
+    }
 }