Add Java Platform Module System (JPMS) Support

function-maven-plugin/src/main/java/com/google/cloud/functions/plugin/RunFunction.java のハードコードされた classpath 設定から始めます。Invoker CLI と Maven/Gradle プラグインがどのように関数を起動するかを追跡し、次に module-path の設定を cloud runtime にどのように渡す必要があるかを判断します。完了には、ローカル呼び出し、ビルドツール、cloud execution にわたる連携したサポートが必要です。

Add support for running functions on the module path (--module-path) instead of only the classpath (--classpath) to enable full Java Platform Module System (JPMS) features in the Functions Framework.

Currently, the Functions Framework for Java only supports classpath-based execution, which prevents developers from utilizing JPMS features at runtime even when their code is properly modularized with module-info.java files.

Modern Java applications using JPMS face the following issues:

1. module-info.java files are ignored at runtime (treated as regular classes on classpath)
2. provides...with service provider declarations don't work, requiring fallback to legacy META-INF/services files
3. Module encapsulation and strong accessibility rules are not enforced
4. No module-level dependency management or version conflict resolution
5. Cannot leverage jlink to create optimized custom runtime images with only required modules, resulting in larger deployment artifacts

This feature request requires changes across three layers:

1. Local Development (Invoker CLI) - Add --module-path support
2. Build Tooling (Maven/Gradle plugins) - Add module-path configuration (right now classpath is hardcoded here
3. Cloud Runtime Infrastructure - Update Google Cloud Functions runtime to support modular execution