Make the URL cleaner and more user friendly

[dpasque]

What Does This PR Add/Change?

Don't ya just hate when you go to Bugomattic, make one teeny, innocent change, and then get steamrolled by a URL that looks like the green symbols from the Matrix? I sure do!

It's time to make our state-tracking URL more user-friendly!

**Note, these changes are actually quite small. I just updated some static string values, and that corresponded to a lot of file updates!

Here's how our URL is now better:

• We don't track falsy values or empty arrays.
• For more parameter-like state, we don't track the value if it's the default. The notable exception are the activePage and the activeReportingStep. (These feel more like navigation values, so hiding the default felt weird. Although I feel that way much more so about activeStep than activeReportingStep. What do you think?)
• For objects, we use "dot" notation instead of brackets. Fullstops don't need to be encoded, so I think this reads wayyyyy nicer.
• I simplified the values for all our pre-defined string types (like IssueType and ActivePage) and switched from camelCase values to kebab-case values. I think that will be more user-friendly for manual editing!
• I changed the order of the state keys in the URL

Testing Instructions

• Unit tests still pass
• Navigate through the app, and see how the URL now looks

Note: the search term appears to be borked, and was so before this change. I've written up the issue in #93 and will fix it in another PR 👍

Issues

Related to #
Closes #69

[dpasque]

@worldomonation Awesome! 😄 Thanks for taking a look!!

You've gone from camelCase URL to a dash-case(?) format instead. I think that does make it easier to read in the context of URLs.

Yep, that's a big change! Probably the biggest one though is not tracking the falsy or default values -- mostly this just keeps the number of query params appended to the end to a much smaller number except in really complicated case. I think this will help people feel more comfortable learning all the query params! And it makes conceptual sense: as you add meaningful data to the app, the URL gets correspondingly longer and more data rich (rather than just all at once)