Fix spacing of "-V" command

[emil-eklund]

Fixes spacing used in examples for the "-V" (severity) command.
Incorrect usage will cause the command to fail.

See earlier discussion: Azure/sql-action#235

[prmerger-automator]

@emil-eklund : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 9a30ea2:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/tools/sqlcmd/sqlcmd-utility.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[emil-eklund]

I think this passage is incorrect too, but I've not had the time to verify for all parameters:

Currently, sqlcmd doesn't require a space between the command-line option and the value. However, in a future release, a space may be required between the command-line option and the value.

[Court72]

@dlevy-msft

Can you review the proposed changes?

Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[dlevy-msft]

This appears to be an issue with the tool. Will need some time to investigate.

[emil-eklund]

This appears to be an issue with the tool. Will need some time to investigate.

I agree. But I do also think the documentation should be updated if the following statement is true:

Currently, sqlcmd doesn't require a space between the command-line option and the value. However, in a future release, a space may be required between the command-line option and the value.