Fix NRE on migration from 1.4 -> 1.5 due to Lucene changes

[PBMikeW]

Lucene Search Migration from 1.4 to 1.5 fails due to null reference error.

[Skrypt]

Could you change this also in the 2 other places where I did the same.

if ((bool)included && !(bool)analyzed)

[Skrypt]

Ok, I think I got this. Basically, a field cannot be analyzed and a keyword at the same time.
And previously the settings were:

Included = keyword (Set when the option "Include this element in the index" was checked)
Analyzed = tokenized (Set when the option "Analyzed" was checked)

Now, I believe that we had all the fields as "Keywords" by default which was the opposite of what ElasticSearch does. Also, it was not making any sense to have it set as a Keyword by default because most people will want these fields to be tokenized/analyzed by default because that's the goal of it ... You want to have only fewer specific fields to be set as Keyword for using them as technical values most of the time.

Based on the fact that "Analyzed" is now the option when you check "Include this element in the index".

old value	new value	comment
!included + analyzed	included	This was impossible to happen but we never know
included + analyzed	included	Here we were specifying that we want the field to be analyzed
included + !analyzed	keyword
included	keyword	same as previous but with a null Analyzed value

So we need to take into consideration that the "Analyzed" option is now "Included". We don't need to migrate the "Included" to a different value just set the new "Keyword" one based on which of these fields had only "Included" set on them.

I did the changes