fix(bundler): Make parsing of dependency output more robust

When fetching e.g. GitHub dependencies, the console output is slightly
different. Instead of adopting the lines to drop, suppress them
completely.

As now no leading text is printed, the concatenation of printed specs
can also be simplified so that it produces no leading null character.

Signed-off-by: Sebastian Schuberth <[email protected]>

plugins/package-managers/bundler/src/main/kotlin/Bundler.kt

@@ -313,7 +313,7 @@ class Bundler(
 
         // The metadata produced by the "resolve_dependencies.rb" script separates specs for packages with the "\0"
         // character as delimiter.
-        val gemSpecs = stdout.split('\u0000').dropWhile { it.startsWith("Fetching gem metadata") }.map {
+        val gemSpecs = stdout.split('\u0000').map {
             GemSpec.createFromMetadata(yamlMapper.readTree(it))
         }.associateByTo(mutableMapOf()) {
             it.name

plugins/package-managers/bundler/src/main/resources/resolve_dependencies.rb

@@ -33,9 +33,10 @@
 
 # This command tries to resolve dependencies that are specified in the Gemfile of the current working directory.
 # Explicitly enable resolution of remote `gem` or `git` dependencies. `path` dependencies are still resolved locally.
-Bundler.definition.resolve_remotely!
+puts Bundler.ui.silence {
+    Bundler.definition.resolve_remotely!
 
-Bundler.definition.specs.each do |spec|
-  puts("\0")
-  puts(spec.to_yaml)
-end
+    # Resolving is triggered lazily, so the below "to_yaml" call might be the place where progress output needs to be
+    # silenced in addition to the above "resolve_remotely" call.
+    Bundler.definition.specs.map { |spec| spec.to_yaml }.join("\0")
+}