Rules do not scan dependency injection without a handler

Problem: You can run standard Spring Boot applications via the [Serverless Java Container](https://github.com/aws/serverless-java-container) or the [Lambda Web Adapter.](https://github.com/awslabs/aws-lambda-web-adapter) In that case, no specific handler interface needs to be implemented. Currently the SnapStart rules would therefore not recognize any violation of the rules:

```java
public class UnicornControllerHandler {

private final UnicornService unicornService;
private final UUID uuid;
private static final Logger logger = LoggerFactory.getLogger(UnicornControllerHandler.class);

public UnicornControllerHandler(UnicornService unicornService) {
this.unicornService = unicornService;
uuid = UUID.randomUUID();
}
}

```

This is somehow related to https://github.com/aws/aws-lambda-snapstart-java-rules/issues/24 but the checks seem to only apply when the class and the method have a specific name.

首先追蹤目前依賴類別或方法具有特定 handler 名稱的 SnapStart 規則檢查，然後將其與 issue 中的依賴注入範例進行比較。當使用 Serverless Java Container 或 Lambda Web Adapter 的標準 Spring Boot 應用程式能夠被掃描，並且無需特定的 handler 介面即可識別違規時，即表示完成。

由索引模型根據 Issue 內容生成。