Remove unneeded TODO for SetScissorRect in unittests

This change also fixed a small style issue in dawn.json.

BUG=

Change-Id: I731aca5558ebe1eb0d6bd144a0e2a9b01963558a
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/6261
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Commit-Queue: Corentin Wallez <cwallez@chromium.org>

dawn.json

@@ -553,8 +553,8 @@
     "filter mode": {
         "category": "enum",
         "values": [
-            {"value": 0, "name":"nearest"},
-            {"value": 1, "name":"linear"}
+            {"value": 0, "name": "nearest"},
+            {"value": 1, "name": "linear"}
         ]
     },
     "float": {

src/tests/unittests/validation/DynamicStateCommandValidationTests.cpp

@@ -62,8 +62,6 @@ TEST_F(SetScissorRectTest, EmptyScissor) {
 }
 
 // Test to check that a scissor larger than the framebuffer is allowed
-// TODO(cwallez@chromium.org): scissor values seem to be integers in all APIs do the same
-// and test negative values?
 TEST_F(SetScissorRectTest, ScissorLargerThanFramebuffer) {
     DummyRenderPass renderPass(device);