HPCC-11253 Do not lock superfiles in roxie

In place of locking superfiles, we subscribe to them so that if they change
any queries using them are automatically reloaded.

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-11253 Do not lock superfiles in roxie

When a query is reloaded due to a file change (or a package change, come to
that), any queries that are already in flight may continue to send slave
requests.

By delaying the release of the previous versions fo the slave queries,
in-flight queies should be able to complete.

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-11253 Do not lock superfiles in roxie

Fix issues spotted in code review

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-11253 Do not lock superfiles in roxie

More issues spotted in code review and testing.

Make sure that dynamic lookups DO lock the superfile (to ensure consistency
across the cluster).

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-11253 Do not lock superfiles in roxie

Fix closedown issues with dalayedReleaser thread.

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-11253 Do not lock superfiles in roxie

DelayedReleaserThread was waking up too often.

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Merge pull request #5738 from richardkchapman/roxie-nolock

HPCC-11253 Do not lock superfiles in roxie

Reviewed-by: Gavin Halliday <ghalliday@hpccsystems.com>