refresh of entity can overwrite pending changes

[njr-11]

The Jakarta Data implementation needs to avoid requesting an entity refresh because it can overwrite changes that haven't been flushed to the database yet.

Also, remove disabled code that creates a load graph and conditionally applies it to queries, which was an experimental approach that we decided not to go with because it overrides the entity's requested fetch behavior that was assigned by the user.

• I have considered the risk of behavior change or other zero migration impact (https://github.com/OpenLiberty/open-liberty/wiki/Behavior-Changes).
• If this PR fixes an Issue, the description includes "Fixes #FILLMEIN" or "Resolves #FILLMEIN" (verify release bug label if applicable: https://github.com/OpenLiberty/open-liberty/wiki/Open-Liberty-Conventions).
• If this PR resolves an external Known Issue (including APARS), the description includes "Fixes #FILLMEIN" or "Resolves #FILLMEIN".

[njr-11]

!build
notification=newcomment

[LibbyBot]

Your Open Liberty Personal Build request is at https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?pipelineId=d79760b4-6a7a-4be2-a276-837821ac3111

Note: Target locations of links might be accessible only to IBM employees.

[LibbyBot]

Code analysis and actions

DO NOT DELETE THIS COMMENT.

• 5 product code files were changed.
• Please describe in a separate comment how you tested your changes.

[LibbyBot]

https://libh-proxy1.fyre.ibm.com/cognitive/pipelineAnalysis.html?pipelineId=d79760b4-6a7a-4be2-a276-837821ac3111 - Open Liberty Personal Build completed with errors/failures.

[njr-11]

The build has 2 intermittent tests failures that are duplicates of a preexisting issue.