Small fixes regarding high-level requirement generation (#295)

Corrects the config location used for determining if we should generate
high-level requirements and adds the requirement module/unit as a backup
group to group requirements under before falling back to "Unknown
Function".

Author: ThisCakeIsALie

src/extension.ts

@@ -2486,7 +2486,7 @@ async function generateRequirements(enviroPath: string) {
     }
   }
 
-  const config = vscode.workspace.getConfiguration("vectorcastTestExplorer");
+  const config = vscode.workspace.getConfiguration("vectorcastTestExplorer.reqs2x");
   const generateHighLevelRequirements = config.get<boolean>(
     "generateHighLevelRequirements",
     false
@@ -3148,7 +3148,7 @@ function generateRequirementsHtml(requirements: any[]): string {
   // Group requirements by function
   const requirementsByFunction: Record<string, any[]> = {};
   for (const req of requirements) {
-    const funcName = req.Function || "Unknown Function";
+    const funcName = req.Function || req.Module || "Unknown Function";
     if (!requirementsByFunction[funcName]) {
       requirementsByFunction[funcName] = [];
     }