fix: Provide a more meaningful error when whitelist entry is missing

In warp-drive-data/warp-drive#8101 it was noted that the error message provided here did not give enough context for users to understand the issue was due to the Fastboot environment and the existence of the fastbootDependencies allow list. This should help greatly with that.

Ref: warp-drive-data/warp-drive#8101 (comment)

Author: runspired

packages/fastboot/src/fastboot-schema.js

@@ -189,17 +189,17 @@ function buildWhitelistedRequire(whitelist, distPath, isLegacyWhitelist) {
         }
       } else {
         throw new Error(
-          "Unable to require module '" + moduleName + "' because it was not in the whitelist."
+          "Unable to require module '" + moduleName + "' in Fastboot because it was not explicitly allowed in 'fastbootDependencies' in your package.json."
         );
       }
     }
 
     throw new Error(
       "Unable to require module '" +
         moduleName +
-        "' because its package '" +
+        "' in Fastboot because its package '" +
         packageName +
-        "' was not in the whitelist."
+        "' was not explicitly allowed in 'fastbootDependencies' in your package.json."
     );
   };
 }