)

This commit resolves Issue #103 where the OGNL parser would fail to parse
class references containing reserved keywords (like "or", "and", "not", etc.)
in package names.

Problem:
--------
Expressions like `@jp.or.example.IdUtils@generateId()` would fail at parse
time with ExpressionSyntaxException because "or" was tokenized as a keyword
rather than as part of the package name.

Root Cause:
-----------
In JavaCC, string literals used as operators in grammar productions (e.g.,
"or" for logical OR) become implicit keyword tokens that take precedence
over generic IDENT tokens during lexical analysis.

Solution:
---------
- Added new `classNamePart()` production that accepts either IDENT tokens
  or any reserved keywords, treating them as identifiers in the context
  of class/package names
- Updated `className()` production to use `classNamePart()` instead of
  direct IDENT references
- Updated `instanceof` production similarly to handle keywords in type names

Changes:
--------
- Modified: ognl/src/main/javacc/ognl.jj
  - Added classNamePart() helper production (lines 1389-1418)
  - Updated className() to use classNamePart() (lines 1374-1382)
  - Updated instanceof production to use classNamePart() (lines 948-969)

- Added: ognl/src/test/java/ognl/test/PackageKeywordTest.java
  - Comprehensive test coverage for keywords in package names
  - Tests for: or, and, not, in, and multiple keywords
  - Validates that parsing succeeds (no ExpressionSyntaxException)

- Added: ISSUE_103_ANALYSIS.md
  - Detailed analysis of the problem and solution
  - Impact analysis and backward compatibility notes
  - Build and verification instructions

Impact:
-------
- Fully backward compatible (only expands valid expressions)
- No ambiguity introduced (context is unambiguous)
- Keywords remain functional as operators in expression contexts
- Aligns with real-world Java package naming (e.g., jp.or.* domains)

Testing:
--------
The fix requires regenerating the parser via `mvn compile` which runs the
javacc-maven-plugin. All existing tests should continue to pass.

Fixes #103