Revert URL encoding when fetching lineage

[jlukenoff]

Problem

When I converted this to use the URLSearchParams in #2525, we started inadvertently url-encoding the node id, which causes problems if the node id contains special characters.

Solution

This reverts node ID from being URL encoded and allows the backend to successfully return the lineage details even when the node ID contains special characters.

Checklist

• You've signed-off your work
• Your changes are accompanied by tests (if relevant)
• Your change contains a small diff and is self-contained
• You've updated any relevant documentation (if relevant)
• You've included a one-line summary of your change for the CHANGELOG.md (Depending on the change, this may not be necessary).
• You've versioned your .sql database schema migration according to Flyway's naming convention (if relevant)
• You've included a header in any source code files (if relevant)

[codecov]

Codecov Report

Merging #2529 (6604314) into main (6814e18) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main    #2529   +/-   ##
=========================================
  Coverage     83.80%   83.80%           
  Complexity     1233     1233           
=========================================
  Files           235      235           
  Lines          5625     5625           
  Branches        270      270           
=========================================
  Hits           4714     4714           
  Misses          767      767           
  Partials        144      144           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[phixMe]

Thanks @jlukenoff for this and the test!