Small fixes [failing due to LIBSVM compat bound]

[tlienart]

• addresses Update RandomForestRegressor input_scitype #154 (randomforest* input scitype) + a fix for LinearRegressor in GLM

[tlienart]

Not passing due to shitty compat bounds on LIBSVM... I don't think we can put explicit requirements on optional packages...

ERROR: Unsatisfiable requirements detected for package LIBSVM [b1bec4e5]:
 LIBSVM [b1bec4e5] log:
 ├─possible versions are: [0.2.0, 0.3.0-0.3.1] or uninstalled
 ├─restricted to versions * by an explicit requirement, leaving only versions [0.2.0, 0.3.0-0.3.1]
 └─restricted by compatibility requirements with Compat [34da2185] to versions: uninstalled — no versions left
   └─Compat [34da2185] log:
     ├─possible versions are: [1.0.0-1.0.1, 1.1.0, 1.2.0, 1.3.0, 1.4.0, 1.5.0-1.5.1, 2.0.0, 2.1.0, 2.2.0, 3.0.0] or uninstalled
     └─restricted to versions 3.0.0 by an explicit requirement, leaving only versions 3.0.0

[ablaom]

Good catch!

[ablaom]

I don't understand this at all.

LIBSVM.jl has no Project file, only a REQUIRE file. According to the old julia documentation the versions specified there are just lower bounds. Since it specifies "Compat 0.41.0" there should be no prohibition on Compat 3.0, right? Indeed this is confirmed by previous builds of MLJModels, where testing (of LIBSVM wrapper) carried on happily with Compat 2.2. But, if in a new environment I add MLJModels (which puts Compat 3.0 in the manifest) then doing add LIBSVM forces Compat to drop from 3.0 to 2.2. Why?

[ablaom]

Just restarting the build after merging #159