How to run `google/fhir-data-pipes/pipelines/batch` uber JAR in Google Cloud Functions locally?

I tried the following command after building the uber JAR of [`google/fhir-data-pipes/pipelines/batch`](https://github.com/google/fhir-data-pipes/tree/master/pipelines/batch):
```bash
java -jar java-function-invoker-1.3.1.jar \
--classpath /d/SourceCodes/google/fhir-data-pipes/pipelines/batch/target/batch-bundled.jar \
--target com.google.fhir.analytics.FhirEtl
```

and here is the error logs:
```
2023-11-23 16:19:50.971:INFO::main: Logging initialized @96ms to org.eclipse.jetty.util.log.StdErrLog
Exception in thread "main" java.lang.RuntimeException: Could not determine function signature type from target com.google.fhir.analytics.FhirEtl. Either this should be a class implementing one of the interfaces in com.google.cloud.functions, or the environment variable FUNCTION_SIGNATURE_TYPE should be set to "http" or "event".
at com.google.cloud.functions.invoker.runner.Invoker.servletForDeducedSignatureType(Invoker.java:393)
at com.google.cloud.functions.invoker.runner.Invoker.startServer(Invoker.java:298)
at com.google.cloud.functions.invoker.runner.Invoker.startServer(Invoker.java:244)
at com.google.cloud.functions.invoker.runner.Invoker.main(Invoker.java:127)
```

Also, how to pass arguments to the uber JAR of the function in question? For example, if running the uber JAR directly, we can do it like this:
```bash
PATH_TO_THE_UBER_JAR=/d/SourceCodes/google/fhir-data-pipes/pipelines/batch/target/batch-bundled.jar && \
java -jar ${PATH_TO_THE_UBER_JAR} \
--fhirServerUrl=http://fhir-server-bkkbn:8092/fhir \
--resourceList=Patient,Practitioner \
--fhirSinkPath=http://fhir-server-central:8098/fhir
```

More advanced, can we use Google Cloud Functions parallelism and supply different arguments values?

Comece pelo ponto de entrada de pipelines/batch com.google.fhir.analytics.FhirEtl e pelo comando java-function-invoker mostrado na issue. Verifique como esse destino é exposto ao Google Cloud Functions, como os argumentos são configurados e se as invocações paralelas aceitam valores diferentes; documente as etapas compatíveis de invocação e configuração local.

Escrita pelo modelo de indexação a partir do texto da issue.