fix: make URLToStringConversion generate URI.create(String).toURL() instead of new URL(String) - #4044

@yvasyliev In general, I agree that URI.create(...).toURL() should be preferred. However, changing the current implementation has some implications. Instead of always throwing a MalformedURLException, it may now throw anIllegalArgumentException. Additionally, URL would no longer be imported automatically, which could break existing expression blocks.

We'll discuss internally whether to include this change in the upcoming release.
@filiphr, what do you think?

@hduelme I think that it is actually fine to do this. If using the constructor is not the recommended way of creating URLs then we should not stand in the way. We should only mention this in our release notes.

However, changing the current implementation has some implications. Instead of always throwing a MalformedURLException, it may now throw an IllegalArgumentException

People will always have the option of writing their own mapping if they want to keep this behaviour

Additionally, URL would no longer be imported automatically, which could break existing expression blocks.

That's completely fine @hduelme. People should not be relying on how we generate the code for their expressions. We also have Mapper#imports that people can use to import what they need always.

So I would say that we should go ahead and merge this