Fix to deprecated the configFile option in the pacakage command

[abetomo]

Even if you specify it in the current specification, nothing has any effect.
Therefore, I thought that it might be good to abolish it, but what do you think?

Since sudden deletion has a big influence, we have issued a warning once.

Relation: #246

[DeviaVir]

👍 sounds good to me, but looks like we'll have to cut another release soon so we have this deployed before actually removing it.

[abetomo]

Thank you!

[monsonjeremy]

@abetomo I'm curious why this option was removed, and what users who use only the package command should do? I do not deploy with the deploy command but rather a custom shell script. Is there anyway to include the environment variables in the package command?

[abetomo]

@monsonjeremy The package option creates a zip file to deploy to Lambda.
You do not need to include environment variables in the zip file.

Environment variables are set from the API or web console.

Previously, there was no way to set environment variables in Lambda, so I included it in my code when creating the zip file.
This option is for that.
This option has been removed now that you can set environment variables.