'stack new' shares all 'stack init' options

I just noticed that whatever options are being added to `stack init` are appearing in `stack new` as well :

```
cueball$ stack new --help
Usage: stack new PACKAGE_NAME [--bare] [TEMPLATE_NAME] [-p|--param KEY:VALUE]
[--solver] [--omit-packages] [--force] [--ignore-subdirs]
[DIRS] [--help]
Create a new project from a template. Run `stack templates' to see available
templates.

Available options:
PACKAGE_NAME A valid package name.
--bare Do not create a subdirectory for the project
TEMPLATE_NAME Name of a template or a local template in a file or a
URL. For example: foo or foo.hsfiles or ~/foo or
https://example.com/foo.hsfiles
-p,--param KEY:VALUE Parameter for the template in the format key:value
--solver Use a dependency solver to determine extra
dependencies
--omit-packages Exclude conflicting or incompatible user packages
--force Force overwriting an existing stack.yaml
--ignore-subdirs Do not search for .cabal files in sub directories
DIRS Directories to include, default is current directory.
--help Show this help text
```

I guess we do not need all the init related options here. Do we even need any of them? Instead of using the initOpts parser in the new command shouldn't we should just construct a hardcoded initOpts structure for the new command?