Update Java inspection to use "@" prefix on field members

[mattrpav]

Java class inspection edge case - field and setter/getter conflict

Scenario:

1. Java class contains an int field named "myInt" with no getter/setter operating on an Integer/int type
2. Java class contains methods named String getMyInt()/setMyInt(String myInt)
3. Need a merge strategy when there are two potential AtlasMap "Fields" that have the same name

Note: An approach could be to use "@" to indicate field vs method

ie..

/Address/@street <-- Java field
/Address/street <-- Java get/set method

Advanced use case:
Extended class implements same field as super class

Result, 2 field definitions:

• /Address/@street <-- Class
• /Address/@street?fieldIsSuperClass=true . <-- SuperClass