Remove incorrect comment about a test mock.

I had thought calls using _getConfig were slow because they triggered
an expensive copy in the ApPipeTask constructor. Instead, _getConfig
is slow because Config construction is slow.

tests/test_driver.py

@@ -118,7 +118,7 @@ def setUpMockPatch(self, target, **kwargs):
         self.addCleanup(patcher.stop)
         return mock
 
-    # Mock up ApPipeTask to avoid doing any processing. _getConfig patch may be unneccessary after DM-13602
+    # Mock up ApPipeTask to avoid doing any processing.
     @unittest.mock.patch("lsst.ap.verify.pipeline_driver._getConfig", return_value=None)
     @patchApPipe
     def testRunApPipeReturn(self, _mockConfig, mockClass):
@@ -131,7 +131,7 @@ def testRunApPipeReturn(self, _mockConfig, mockClass):
         self.assertEqual(len(metadata.paramNames(topLevelOnly=False)), 1)
         self.assertEqual(metadata.getScalar("lsst.ap.pipe.ccdProcessor.cycleCount"), 42)
 
-    # Mock up ApPipeTask to avoid doing any processing. _getConfig patch may be unneccessary after DM-13602
+    # Mock up ApPipeTask to avoid doing any processing.
     @unittest.mock.patch("lsst.ap.verify.pipeline_driver._getConfig", return_value=None)
     @patchApPipe
     def testRunApPipeSteps(self, _mockConfig, mockClass):
@@ -168,7 +168,7 @@ def testUpdateMetricsReal(self):
 
         self.assertEqual(self.job.measurements, self.subtaskJob.measurements)
 
-    # Mock up ApPipeTask to avoid doing any processing. _getConfig patch may be unneccessary after DM-13602
+    # Mock up ApPipeTask to avoid doing any processing.
     @unittest.mock.patch("lsst.ap.verify.pipeline_driver._getConfig", return_value=None)
     @patchApPipe
     def testUpdateMetricsOnError(self, _mockConfig, mockClass):