Update shipped modin to 0.3.1

[williamma12]

What do these changes do?

Update modin to 0.3.1 to resolve the issue of getting a ModuleNotFoundError: No module named 'dask' when trying to import modin

Related issue number

#3998

[AmplabJenkins]

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Ray-PRB/11986/
Test FAILed.

[robertnishihara]

Why does this fix the problem?

[williamma12]

The error that we've been getting on ray is that it complains about not having dask installed, which gets fixed in modin 0.3.1.

…

On Thu, Feb 14, 2019 at 11:42 PM Robert Nishihara ***@***.***> wrote: Why does this fix the problem? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4058 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALzfVU-QosQGLgdHk70AITSatsE-locaks5vNmT1gaJpZM4a88F5> .

[robertnishihara]

In the issue #3998 it says that the error is ModuleNotFoundError: No module named 'modin'.

[williamma12]

In the issue #3998 it says that the error is ModuleNotFoundError: No module named 'modin'.

Oops, I misremembered the issue. Either way, this pr is necessary to avoid getting dask import errors when trying to use the version of modin that ships with ray