Avoid using Lucene deprecated methods when not essential for 5.8 API

Description

We're using deprecated methods and types from Apache Lucene; in most cases this is caused by the lack of better alternatives which we can't avoid w/o removing currently supported features, especially things exposed over our public API in version 5.8.

In some internal cases this is avoidable and it would be a good time to reduce the amount of such cases, so that we're not overwhelmed by deprecation warnings and can still keep a critical eye on the reamining ones.

Environment

None

Status

Assignee

Sanne Grinovero

Reporter

Sanne Grinovero

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Fix versions

Priority

Major
Configure