mapchooser: Set minimum number maps to include in vote

[stickz]

This commit allows the user to have a consistent minimum number of maps in the vote, regardless how many previous maps are excluded. It also improves the handling of the situation, when the number of previous maps to exclude is set higher than the number of available maps. Instead of excluding no previous maps, it will exclude until the minimum include count is reached.

[KyleSanderson]

The other quantity checks seem okay, but fundamentally this is dangerous and not correct. We should have indexes that need to be removed if needed and this provides the expected fast path for basic programming.

[KyleSanderson]

This is not correct. There's no reason to triple scan the array.

[stickz]

There are 2 ArrayList classes being worked with here. I don't see a "fast path" to just remove an index.

g_OldMapList is an array ordered from least to most recently played.
tempMaps is a working array from g_MapList which is a random order.

I think it's required to search for the string that needs to be removed in tempMaps.

The code gets the string at index i from g_OldMapList. Then gets the index of the string in tempMaps. Afterwards, it erases the index from tempMaps if the string was found in the ArrayList.