Improve the `init` task when in interactive mode when a Maven build is present in the current directory, by first asking the user if they would like to generate a Gradle build for the Maven build. If the user answers 'yes', proceed without asking any further questions. If the user answers 'no', only then ask the user to select which type of build they would like to create.
Change the `init` task to improve the interactive experience when converting a Maven build. - Do not suggest `pom` as a build type when there is no `pom.xml` present, as the conversion makes no sense in this case. - Do not prompt for a DSL or project name when converting a Maven build, as these are not supported or ignored by the Maven build conversion. - When the `--project` or `--package` options are used with the `init` task, fail when the selected build type does not support these options, e.g. when converting to Maven build.