fix: support inline helper objects in Container.create

- Added detection for inline helper objects (objects with callable methods)
- Inline helpers are now used directly without module loading
- Distinguishes between inline helpers and empty config objects
- Fixes AsyncWrapper test that uses inline TestHelper

This resolves the 'Cannot find module TestHelper' error when creating
containers with inline helper objects for testing purposes.

Test results: 487 passed, 1 failed (pre-existing BDD timeout), 16 skipped

Author: kobenguyent

lib/container.js

@@ -333,6 +333,19 @@ async function createHelpers(config) {
         helperName = HelperClass.constructor.name
       }
 
+      // Check for inline helper object (plain object with callable methods, no require field)
+      // Inline helpers have methods defined directly on them, unlike config objects
+      if (!HelperClass && !config[helperName].require && typeof config[helperName] === 'object') {
+        // Check if this object has any callable methods (indicates it's an inline helper)
+        const hasMethods = Object.values(config[helperName]).some(val => typeof val === 'function')
+        if (hasMethods) {
+          // This is an inline helper object, use it directly
+          helpers[helperName] = config[helperName]
+          debug(`helper ${helperName} loaded as inline object`)
+          continue
+        }
+      }
+
       // classical require - may be async for ESM modules
       if (!HelperClass) {
         // requireHelperFromModule is async, so we need to await it
@@ -343,9 +356,7 @@ async function createHelpers(config) {
           HelperClass = HelperClass.default
           debug(`extracted default export for ${helperName}`)
         }
-      }
-
-      // handle async CJS modules that use dynamic import
+      } // handle async CJS modules that use dynamic import
       if (isAsyncFunction(HelperClass)) {
         helpers[helperName] = {}