and remove obsolete code relating to reassociation from lock() and refresh()

also remove code for reattaching proxies during flush

This appears to be a very ancient bug. If another type with the same
name is imported, we have to qualify the type name, even if it is in
the same package or in java.lang.

…e Next

Fixes quarkusio/quarkus#50178

I added the indexQueryInterfaces method before the elements were
recursively visited to find nested entities. I did not realise we were
visiting nested types twice: once with the primaryEntity set (by
indexQueryInterfaces) and the second time without it, causing issues
with nested repositories losing their primaryEntity in Quarkus Panache.

I'm now removing indexQueryInterfaces in favour of the upstream
recursion, adapted for keeping track of implicit primaryEntity.

…@delete queries

This only happens in Quarkus Panache when we have an implicit JD
repository with a @delete query method, because jakartaDataRepository is
not set, but it should not matter, because this method is only defined
by JD for repositories, so I don't think it makes any sense for it to be
false.

The result was code like this:

@OverRide
public long deleteByTitle(String title) {
        var _builder = session.getCriteriaBuilder();
        var _query = _builder.createCriteriaDelete(Panache2Book.class);
        var _entity = _query.from(Panache2Book.class);
        _query.where(
                        title==null
                                ? _entity.get(Panache2Book_.title).isNull()
                                : _builder.equal(_entity.get(Panache2Book_.title), title)
        );
        try {
                return session.createMutationQuery(_query).executeUpdate();
}

Note the missing catch. This is because the catch is conditional on
jakartaDataRepository while the try is not conditional.