Lucene index locking

Lucene Index updates have been overhauled in order to gain performance efficiencies and reduce errors:

• system now cumulatively collects all affected product codes and then batch processes them via asynchronous operation that does not block end-user UI responsiveness.
• record processing efficiency has been improved by restricting some of the data retrieved from the database to only relevant products.
• safeguard functionality has been added in the event of the operation not being able to run at time of initiation, which can occur if a scheduled task is already running a lucene index operation in the background. In this case, the updated products are stored in a queue table for later processing.