cli: Fix deployment CLI not working with deploy . -f config.yaml

[jianshen92]

What does this PR address?

bentoml deploy . -f config.yaml ignores the config file passed in.

Fixes #(issue)

Before submitting:

• Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's
  guide on how to create a pull request.
• Does the code follow BentoML's code style, pre-commit run -a script has passed (instructions)?
• Did you read through contribution guidelines and follow development guidelines?
• Did your changes require updates to the documentation? Have you updated
  those accordingly? Here are documentation guidelines and tips on writting docs.
• Did you write tests to cover your changes?

[jianshen92]

Removing self.name here

[Haivilo]

Are we removing self.name or self.bento?

[jianshen92]

Sorry, I meant removing self.bento

[FogDong]

Why we need to remove self.bento here?

[frostming]

Otherwise it would be rejected by the check:

if (
            (self.config_dict and self.config_file)
            or (self.config_dict and deploy_by_param)
            or (self.config_file and deploy_by_param)
        ):
            raise BentoMLException(
                "Configure a deployment can only use one of the following: config_dict, config_file, or the other parameters"

[jianshen92]

Because bentoml deploy . will consider . as the bento and this check evaluates to true and then it will skip the file argument

[frostming]

I am afraid you can't judge with this, given there are integer values (scaling_min and scaling_max)
Can we just filter None, meaning it is specified by the users

[jianshen92]

Yeah initially that was the case, but the default for self.envs is a list so it will always evaluate to True if we dont check for it.

[jianshen92]

Decided to throw error if user use both inline argument and file.
User should specify the name in the bentofile, i.e name: '.'

CC: @Sherlock113 to update documentation