Encode exported Query file paths

[melton-jason]

Fixes #5069

Note:
The Export process still completely fails if the Query name contains / (the character is interpreted as part of the file path).

Checklist

• Self-review the PR after opening it to make sure the changes look good
  and self-explanatory (or properly documented)
• Add relevant issue to release milestone

Testing instructions

• Save and export query with # in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name
• Save and export query with ? in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name

For other special characters: @$%&+?\=;,":

• Save a Query containing one or more of the characters
• Ensure that Query export files can still be downloaded, the entire query name is present in the file name (special characters are either present in the download file name or replaced with _)

[maxpatiiuk]

looks good - do we need to do this anywhere else? (i.e other notifications that have files)

[melton-jason]

looks good - do we need to do this anywhere else? (i.e other notifications that have files)

@maxpatiiuk
We could do this for other notifications with files, but this was not strictly needed as all other file names can not be generated with these characters: their file names contain no user input.

Though yes, it's probably best we eliminate this bug in the other places before it becomes a problem. I'll push a fix for those files too.

[Areyes42]

Testing instructions

• Save and export query with # in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name
• Save and export query with ? in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name

For other special characters: @$%&+?\=;,":

• Save a Query containing one or more of the characters
• Ensure that Query export files can still be downloaded, the entire query name is present in the file name (special characters are either present in the download file name or replaced with _)

---

I tested with various special characters, and they work with both unselected and selected queries.

One thing that I noticed unrelated to this PR — creating a CSV from selected query fields doesn't trigger the same notification download behavior. Is this expected?

Screen.Recording.2024-07-08.at.11.59.25.AM.mp4

[lexiclevenger]

Testing instructions

• Save and export query with # in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name
• Save and export query with ? in the query's name
• Export the query as a CSV/KML (without selected any Query Results)
• Ensure the file can be downloaded and the full query name is in the downloaded file's name

For other special characters: @$%&+?\=;,":

• Save a Query containing one or more of the characters
• Ensure that Query export files can still be downloaded, the entire query name is present in the file name (special characters are either present in the download file name or replaced with _)

---

Looks good! The file names are exported correctly.

[lexiclevenger]

One thing that I noticed unrelated to this PR — creating a CSV from selected query fields doesn't trigger the same notification download behavior. Is this expected?

@Areyes42 I think this is related to #5023