Upgrade Express to v5 + code cleanup

[acalcutt]

This PR addresses #1412 by upgrade express to v5. It also tries to address #1411 by adding Try/Catch around that function and also adding better verbose logging.

express v5 features a new version of 'path-to-regexp', which changes the syntax to no longer allow optional parameters by surrounding them with ( and )? and putting the type inside ( and ). see https://github.com/pillarjs/path-to-regexp?tab=readme-ov-file#errors

Unexpected ? or +
In past releases, ?, *, and + were used to denote optional or repeating parameters. As an alternative, try these:
For optional (?), use an empty segment in a group such as /:file{.:ext}.
For repeating (+), only wildcard matching is supported, such as /*path.
For optional repeating (*), use a group and a wildcard parameter such as /files{/*path}.
Unexpected (, ), [, ], etc.
Previous versions of Path-to-RegExp used these for RegExp features. This version no longer supports them so they've been reserved to avoid ambiguity. To use these characters literally, escape them with a backslash, e.g. "\\(".

In tileserver-gl we had a lot of spots we were using optional parameters and defining types by regex values, which because of this change of 'path-to-regexp' used by express, are no longer supported

This PR tries to address this change by doing the following
1.) All optional parameters have been changed from the format (/:spriteID)?, to the new format {/:spriteID}
2.) All validation has been removed from the enpoints, For example, :range([\d]+-[\d]+) became :range
3.) Because validation was removed from the endpoints, some of our paths under /styles/ became too similar. I had to merge these into a single path and add in some logic to direct the request the right way.
4.) Also because validation was removed I tried to add in some logic for accepted values for things like tileSize and Scale
5.) The syntax we used in ServeTemplate also has to change. the '$' was no longer supported in the path, so it had to be removed. This lead to a need to use next('route') to redirect request not served by the template.

Other changes.
1.) Tried to sanitize outputs. I still wanted some information in the logs, so it tries to at least sanitize the data to acceptable characters. codeql seems to still not like this.
2.) Tried to change variable style functions to traditional functions for better logging information
3.) Added generated function headers so the code is more informative.
4.) Some status codes have change. for example 400 vs 404 when bad data is provided (test had to be updated for this). Also, when a tile is not found it now returns a 204 No Content to try and allow sparse tile suport.

[okimiko]

I just had a short look at the code changes; as far as I have seen it looks OK so far.

I build the image and used it with my test config/data and can see a lot of "Handling request" messages on the application console and for some styles I have errors regarding fonts in the browser console. I would like to take a deeper look at that and test verbose logging a bit. May be I can dig out some older scripts, which use the static endpoint, too.

In addition I would like to apply my elevation fix to this PR and test again. I hope I will have time in the next few days.

[acalcutt]

Do you have verbose enabled in your test config? You should only see the handling messages when verbose is enabled. I added more logging in verbose mode to help troubleshoot this.

[acalcutt]

One concert I have is with fonts. I added a lot of validation there to make codeql happy, but i'm not sure they are all good changes.

[okimiko]

I re-checked everything:

• I start the tileserver with "--verbose", without the logs are fine.
• The font errors I've seen are related to open sans, which I use in my setup (https://bugzilla.mozilla.org/show_bug.cgi?id=1185685)
• I started my map-exporter script, which uses the static endpoint and everything looks fine so far.

[okimiko]

I applied and adjusted changes of #1432 in another branch.

Except the coordinates of fetchTileData (which is fixed in the new branch, too) this PR works for me.

[okimiko]

Use const fetchTile = await fetchTileData(source, sourceType, z, xy[0], xy[1]); instead. This was invalid for pmtiles before.