igniter.new doesn't honour the --module option of mix new.

[jimsynz]

Describe the bug
When running mix help igniter.new it clearly states that any unknown options are passed into the underlying "new task":

Creates a new project using mix new, and adds igniter to the project.

## Options

All options are passed through to mix new, except for:

  • --install - A comma-separated list of dependencies to install using mix
    igniter.install after creating the project.
  • --example - Request example code to be added to the project when
    installing packages.
  • --with - The command to use instead of new, i.e phx.new

However creating a new project and trying to override the derived module name (as per mix help new) results in the option being ignored.

To Reproduce

$ mix igniter.new foobar --module FooBar
* creating README.md
* creating .formatter.exs
* creating .gitignore
* creating mix.exs
* creating lib
* creating lib/foobar.ex
* creating test
* creating test/test_helper.exs
* creating test/foobar_test.exs

Your Mix project was created successfully.
You can use "mix" to compile it, test it, and more:

    cd foobar
    mix test

Run "mix help" for more commands.

$ grep defmodule foobar/lib/foobar.ex
defmodule Foobar do

Expected behavior

The generated modules should begin with the name FooBar not Foobar.

** Runtime

• Elixir version 1.17.0
• Erlang version 27.0
• OS macOS Sequoia 15.0
• Igniter version 0.2.4
• any related extension versions

Additional context
Add any other context about the problem here.

[zachdaniel]

hmmm....did you update to the latest hex archive? i don't see why we'd be ignoring it.

[zachdaniel]

"All options are passed through to mix new, except for:" is a lie. we only pass known options to mix.new, and everything else comes from --with-arts