More lenient behavior for unsupported version formats

In a project like this:

//plugins.sbt
addSbtPlugin("com.disneystreaming.smithy4s" % "smithy4s-sbt-codegen" % "0.13.6")

//build.sbt
val root = project
  .in(file("."))
  .settings(
    libraryDependencies ++= Seq(
      "com.disneystreaming.smithy4s" %% "smithy4s-aws-http4s" % smithy4sVersion.value,
      //other deps
    ),
  )
  .enablePlugins(Smithy4sCodegenPlugin)

The app seems to fail when seeing .value - in this case, the version is set by the plugin but this app probably couldn’t (and shouldn’t) know that - probably the best course of action would be to log a warning but otherwise ignore the version and handle others.

Current behavior:

~/projects/sbt-interactive-update/target/universal/stage/bin/sbt-interactive-update

timestamp=2022-06-27T14:18:48.892822Z level=ERROR thread=#zio-fiber-0 message="" cause="Exception in thread "zio-fiber-" java.lang.Error: Could not find version for com.disneystreaming.smithy4s %% smithy4s-aws-http4s % smithy4sVersion.value
        at dependencies.DependencyParser$$anonfun$$nestedInanonfun$getDependencies$1$1.applyOrElse(DependencyParser.scala:71)"

[kitlangton]

This shall not blow up any longer 😃

[kubukoz]

thanks 😃