Refactor subjob schema for improved consistency and readability

- Removed unnecessary line breaks in the subjob schema to enhance code clarity.
- Ensured all required fields maintain their definitions for better data integrity.
- Updated formatting for the `state` field to align with coding standards.

src/database/schemas/production/subjob.schema.js

@@ -7,40 +7,40 @@ const subJobSchema = new mongoose.Schema({
   printer: {
     type: Schema.Types.ObjectId,
     ref: 'printer',
-    required: true,
+    required: true
   },
   job: {
     type: Schema.Types.ObjectId,
     ref: 'job',
-    required: true,
+    required: true
   },
   moonrakerJobId: {
     type: String,
-    required: false,
+    required: false
   },
   gcodeFile: {
     type: Schema.Types.ObjectId,
     ref: 'gcodeFile',
-    required: true,
+    required: true
   },
   state: {
     type: { required: true, type: String },
-    progress: { required: false, type: Number },
+    progress: { required: false, type: Number }
   },
   number: {
     type: Number,
-    required: true,
+    required: true
   },
   createdAt: {
     type: Date,
-    default: Date.now,
+    default: Date.now
   },
   updatedAt: {
     type: Date,
-    default: Date.now,
+    default: Date.now
   },
   startedAt: { required: false, type: Date, default: null },
-  finishedAt: { required: false, type: Date, default: null },
+  finishedAt: { required: false, type: Date, default: null }
 });
 
 subJobSchema.index({ moonrakerJobId: 'text', 'state.type': 'text' });