Bounding boxes added to priority rules through API get altered.

When I use the API to create or update a challenge that has a bounding box highPriorityRule, the first value (x_min) gets munged.

If add this json to the high priority rule:
{"type": "bounds", "operator": "contains", "value": "-98.805051,29.2562939,-98.023766,29.777227"},

then the resulting high priority rule set in the challenge looks like this:

The full text in the value box is: "805051,29.2562939,-98.023766,29.777227"

The first value seems to be getting altered from what was passed in as I would expect it to be
"-98.805051,29.2562939,-98.023766,29.777227"

From the code I gathered that it thinks that the "value" string is a two part string separated by a "."
So I tried adding a garbage string to my value...
{"type": "bounds", "operator": "contains", "value": "bbox.-98.805051,29.2562939,-98.023766,29.777227"},
And that worked!

Start by tracing the API path for creating or updating a challenge and handling a bounds highPriorityRule value. Reproduce the issue with the two JSON examples, then inspect where the value is split or parsed. Done means the negative x_min is preserved for both create and update requests, with regression coverage if the relevant test location is found.