Update document and email message schemas to allow optional object references

- Modified the `object` field in both `documentJob` and `emailMessage` schemas to be non-required.
- Introduced a new `objects` array field in both schemas to accommodate multiple optional object references, enhancing flexibility in data management.

src/database/schemas/management/documentjob.schema.js

@@ -14,8 +14,15 @@ const documentJobSchema = new Schema(
     object: {
       type: Schema.Types.ObjectId,
       refPath: 'objectType',
-      required: true,
+      required: false,
     },
+    objects: [
+      {
+        type: Schema.Types.ObjectId,
+        refPath: 'objectType',
+        required: false,
+      },
+    ],
     state: {
       type: { type: String, required: true, default: 'queued' },
       progress: { type: Number, required: false },

src/database/schemas/management/emailmessage.schema.js

@@ -13,7 +13,8 @@ const emailMessageSchema = new Schema(
       required: true,
     },
     objectType: { type: String, required: true },
-    object: { type: Schema.Types.ObjectId, refPath: 'objectType', required: true },
+    object: { type: Schema.Types.ObjectId, refPath: 'objectType', required: false },
+    objects: [{ type: Schema.Types.ObjectId, refPath: 'objectType', required: false }],
     emailAccount: {
       type: Schema.Types.ObjectId,
       ref: 'emailAccount',