Check call flows passing JavaProject.NO_RELEASE into multi-release aware methods

During review of #4534 I identified the following call chains as passing `JavaProject.NO_RELEASE` where potentially a specific release should be passed (focus is in NameLookup):

There might be more.

For each of the leaves where `NO_RELEASE` is passed, we need a justification or we need to improve.

Start with the NameLookup call chains shown in the issue and trace each leaf that receives JavaProject.NO_RELEASE. For every leaf, determine whether that value is justified or whether a specific release is needed; the work is done when all identified call sites have that justification or an improvement.

Written by the indexing model from the issue text.