Remove redundant access levels and jobs. (#3360)

We do not need access levels like ResearchDirector when Research | Command works fine.

We also do not need a QM.

Etc...

Resources/Prototypes/AccessLevels/cargo.yml

@@ -1,5 +1,5 @@
-- type: accessLevel
-  id: Quartermaster
+#- type: accessLevel
+#  id: Quartermaster
 
 - type: accessLevel
   id: Cargo

Resources/Prototypes/AccessLevels/engineering.yml

@@ -1,6 +1,6 @@
-- type: accessLevel
-  id: ChiefEngineer
-  name: Chief Engineer
+#- type: accessLevel
+#  id: ChiefEngineer
+#  name: Chief Engineer
 
 - type: accessLevel
   id: Engineering

Resources/Prototypes/AccessLevels/medical.yml

@@ -1,6 +1,6 @@
-- type: accessLevel
-  id: ChiefMedicalOfficer
-  name: Chief Medical Officer
+#- type: accessLevel
+#  id: ChiefMedicalOfficer
+#  name: Chief Medical Officer
 
 - type: accessLevel
   id: Medical

Resources/Prototypes/AccessLevels/research.yml

@@ -1,6 +1,6 @@
-- type: accessLevel
-  id: ResearchDirector
-  name: Research Director
+#- type: accessLevel
+#  id: ResearchDirector
+#  name: Research Director
 
 - type: accessLevel
   id: Research

Resources/Prototypes/AccessLevels/security.yml

@@ -1,12 +1,12 @@
-- type: accessLevel
-  id: HeadOfSecurity
-  name: Head of Security
+#- type: accessLevel
+#  id: HeadOfSecurity
+#  name: Head of Security
 
 - type: accessLevel
   id: Security
 
-- type: accessLevel
-  id: Brig
+#- type: accessLevel
+#  id: Brig
 
-- type: accessLevel
-  id: Detective
+#- type: accessLevel
+#  id: Detective

Resources/Prototypes/AccessLevels/service.yml

@@ -1,11 +1,11 @@
-- type: accessLevel
-  id: Bar
+#- type: accessLevel
+#  id: Bar
 
-- type: accessLevel
-  id: Kitchen
+#- type: accessLevel
+#  id: Kitchen
 
-- type: accessLevel
-  id: Hydroponics
+#- type: accessLevel
+#  id: Hydroponics
 
 - type: accessLevel
   id: Service