Move StatisticsAggregator.cloneGameData as GameDataUtils.cloneGameDataWithHistory Remove

[frigoref]

No description provided.

[frigoref]

Slice from PR #13619

[DanVanAtta]

I think we should approach this fix by enhancing the clone-data-manager rather than "hiding" it.

For historical context, there was previously a method that was: cloneGameData()

Later, someone found that the history could be omitted for a faster clone, the API then became: cloneGameData(true|false). Rather than do that, a builder object was created. This approach was intended to be expanded for any other options. So, we have instead cloneGameData(Options.builder().withHistory(true).build()). Verbose, but an otherwise nice API.

Then.. came along seek. Rather than adding an option, a boolean parameter was added..

The API I think we want is:

cloneGameData(Options.builder().withHistory().withSeek().build())

A) move the 'seek' flag into options

B) remove the boolean variable in the builder (this might be a v2 change, i expect there to be some tests with dependencies on the variable)