fix: process log messages as templates independently of response

Based on the documentation, log messages should always be processed
through the template engine, regardless of whether the response has
template=true. The documentation shows an interceptor example with
placeholders in the log message but no template flag on the response:

```yaml
log: "User accessed ${context.request.headers.User-Agent}"
response:
  statusCode: 401
  content: "Unauthorized"
  # Note: no template: true
```

Changes:
- Log messages are now always processed through PlaceholderUtil
- Removed template: true from test config (not needed for logs)
- Fixed wildcard import in AbstractResourceConfig

This allows log messages to use placeholders independently of whether
the response content uses templating.

Author: claude

core/engine/src/main/java/io/gatehill/imposter/service/ResponseServiceImpl.kt

@@ -228,17 +228,14 @@ class ResponseServiceImpl @Inject constructor(
         } else {
             origResponseData
         }
-        
+
         // Process custom log message if present
+        // Log messages are always processed as templates per documentation
         if (resourceConfig is AbstractResourceConfig && resourceConfig.log != null) {
-            val logMessage = if (template) {
-                PlaceholderUtil.replace(resourceConfig.log!!, httpExchange, PlaceholderUtil.templateEvaluators)
-            } else {
-                resourceConfig.log!!
-            }
+            val logMessage = PlaceholderUtil.replace(resourceConfig.log!!, httpExchange, PlaceholderUtil.templateEvaluators)
             LOGGER.info("Resource log: {}", logMessage)
         }
-        
+
         response.end(responseData)
     }