Correct issue with default.project.json files with no name being named default after change (#917)

Co-authored-by: Kenneth Loeffler <kenloef@gmail.com>

rojo-test/serve-tests/sync_rule_no_name_project/default.project.json

@@ -0,0 +1,17 @@
+{
+  "tree": {
+    "$className": "StringValue",
+    "$properties": {
+      "Value": "This should be named `sync_rule_no_name_project` and have a child at `src/not_a_project`"
+    },
+    "src": {
+      "$path": "src"
+    }
+  },
+  "syncRules": [
+    {
+      "use": "project",
+      "pattern": "*.rojo"
+    }
+  ]
+}

rojo-test/serve-tests/sync_rule_no_name_project/src/not_a_project.rojo

@@ -0,0 +1,8 @@
+{
+    "tree": {
+        "$className": "StringValue",
+        "$properties": {
+            "Value": "If this isn't named `not_a_project`, something has gone wrong!"
+        }
+    }
+}