Fixing issue 916 on URI path interpolation

[jurgenvinju]

• removes deprecated calls and fixes modules names in tests*
• fixes loc splicing does not build URIs the right way (e.g. spaces end up being not encoded when the loc is printed) #916
• add tests for loc splicing does not build URIs the right way (e.g. spaces end up being not encoded when the loc is printed) #916
• add test with interpolation in authority vs interpolation in paths (paying attention to the correct amount of / in the result
• fix problem with difference between authority and path and extra slashes

[jurgenvinju]

This one was open since 2015, but now more and more people get confused by it. It's probably because of the increased usage of clair which has path interpolation in its source code. Seems like a good time as any to fix it. At least we have some tests for it now.

[DavyLandman]

The RascalJUnitTestRunner changes confuse me a bit.

[jurgenvinju]

The current solution is broken. Another test for toLocation shows that the current way of interpolating path strings also introduces an extra / even if the interpolation is in the authority part of a URI.

• Have to figure out a way to see if we are already in the path part somehow during the interpolation process.
• Have to make sure we encode differently in the authority part then in the path part.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jurgenvinju]

We can continue this where we left off in 2023. The current PR improves on the situation, where it encodes interpolated values better than before, but we still have to distinguish better between the "authority" and the "path" part of the URI we are building.