CCM-7465: update comment about forcing dynamically rendered page

Author: bhansell1

frontend/src/app/manage-templates/page.tsx

@@ -1,18 +1,19 @@
 import { NHSNotifyButton } from '@atoms/NHSNotifyButton/NHSNotifyButton';
 import content from '@content/content';
 import { ManageTemplates } from '@molecules/ManageTemplates/ManageTemplates';
-import { Template } from 'nhs-notify-web-template-management-utils';
 import { getTemplates } from '@utils/form-actions';
 
-// Note: this page is forced to be server-side rendered
+// Note: force this page to be dynamically rendered
 // This is because Next defaults this page as a static rendered page
-// which causes a build failure due to getTemplates attempting to get cookies
+// which causes a build failure due to getTemplates attempting to get a server-side session via cookies and failing
+// The other pages which do similar thing expect a templateId parameter
+// Which informs next it needs to be dynamically rendered
 export const dynamic = 'force-dynamic';
 
 const manageTemplatesContent = content.pages.manageTemplates;
 
 export default async function ManageTemplatesPage() {
-  const availableTemplateList: Template[] | [] = await getTemplates();
+  const availableTemplateList = await getTemplates();
 
   return (
     <div className='nhsuk-grid-row' data-testid='page-content-wrapper'>