[BUGFIX beta] Ability to set a query param to a string of "null" when default value is null

[webark]

If a default query parameter is null, we should leave it as null and not switch it to a string value of "null".

This came up when in a controller we had set a default value for a query parameter of search to be null. Then if we tried to do a search for "null" it would not perform the search since it was casting the null value to a string of "null" for the default, and failed the difference check between the new query param and the default.

Didn't see any pertinent tests in the local package tests, so I added a test to the general ember routing query param test.

[webark]

Wondering if there is anything I could do to get this merged in?

[homu]

☔ The latest upstream changes (presumably #14415) made this pull request unmergeable. Please resolve the merge conflicts.

[heat]

Is it the desirable behavior ? I wondering, if you really want a null value you need to just remove the parameter, right ?

[webark]

@heat we came across it when someone named something in the system as "null" and ran a search for "null". Ember ended up removing that query paramater due to the casting that it does.

[homu]

☔ The latest upstream changes (presumably #14433) made this pull request unmergeable. Please resolve the merge conflicts.

[webark]

I think due to nathan's future work with serializing parameters, and the shifting around of this issue, and due to the fact that it's sad dormant for 6 months, I'm going to go ahead and close it as "unmerged".