Release notes for Optimizely updates

When url (UrlSegment) of a page was changed, child pages were not updated in the Find index causing invalid urls to be listed in search results.

Adding .NET 6 support to the Search & Navigation (Find) client.

Fixed an issue that caused a 500 error on an _msearch call while attempting to view search statistics for a specific query. Track ID was supposed to contain [content_type]/[id].

Fixed an issue where adding best bets sent one config request for every existing best bet.
If you have many bests bets it can make adding/editing best bets in the Find UI result in a timeout.

Fixed an issue where the content indexer had a collection of exceptions (called _indexingExceptions), which could cause a memory leak.

Fixed an issue where adding ServiceApi to the project caused the unified search to stop working. (If you removed the ServiceApi nugget, it would work again because of a lack of user and roles in the first request.)

Fixed an issue where sometimes visitors got duplicate hits when paginating, which happened only for non-ordered constant score queries because different shards were answering the same query.

[Netcore] A NullReferenceException exception occurred when adding MapControllerRoute, when the search result should have been returned.

Logging of errors was enhanced to be more informative.

When a culture was set in web.config, the indexing job should have updated the SearchTypeName. For example, setting the culture to Swedish (sv-SE), SearchTypeName should have updated to Sida but was listed incorrectly as Page.