fix(deps): update dependency mssql to v7

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
mssql	^6.2.0 -> ^7.0.0

---

Release Notes

tediousjs/node-mssql

v7.1.3

Compare Source

[fix] Request timeout settings now respect value parsed from connection strings ((#​1257)[tediousjs/node-mssql#1257)

v7.1.2

Compare Source

v7.1.1

Compare Source

[fix] Errors from tedious connection creation now cause connection promise to reject ((#​1254)[https://github.com/tediousjs/node-mssql/pull/1254])
[fix] Encrypt and transaction binding settings now respect value parsed from connection strings ((#​1252)[tediousjs/node-mssql#1252)

v7.1.0

Compare Source

[new] Add parseJSON support to query strings
[fix] Bump various dependencies for security fixes

v7.0.0

Compare Source

[new] Result sets with duplicate keys can now be handled using request.arrayRowMode (#​1130)
[new] Requests in stream mode now emit a rowsaffected event (#​1213)
[new] msnodesqlv8 driver now has detailed error support (#​1212)
[new] Connection validation checks before releasing connections from the pool. This can be turned of via validateConnection: false config option (#​1192)
[new] UseUTC is now supported on msnodesqlv8 connections (#​1222)
[change] Updated to latest Tedious 11
[change] Updated tarnjs to v3
[change] Updated to support latest msnodesqlv8 v2 (#​1157)
[change] Piped streams no longer have errors forwarded on to them (#​1028)
[change] tedious config option trustServerCertificate defaults to false if not supplied (#​1030)
[change] Request.pipe now pipes a true node stream for better support of backpressure (#​1078)
[change] drop support for NodeJS < 10 (#​1070)
[fix] Ensure line endings are unix style (LF)
[fix] Avoid using deprecated .inspect on Objects (#​1071)
[fix] Bump various dependencies for security fixes (#​1102)
[fix] Trailing rows from request streams using msnodesqlv8 driver fail to be emitted (#​1109)
[fix] Issue with geography v2 parsing resolve (#​1138)
[fix] Connection config objects are now deep cloned when stored against a connection pool (#​1217)
[removed] Support for connection uri format has been removed (eg: mssql://user:password@host/?params=values)

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[fhinkel]

@kurtisvg looks like there's a breaking change. Can you have a look? Thanks

[kurtisvg]

@shubha-rajan FYI

[dpebot]

/gcbrun

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[shubha-rajan]

@googlebot I consent.

[dpebot]

/gcbrun

[shubha-rajan]

@GoogleCloudPlatform/nodejs-docs-samples-owners I updated this PR so that the Cloud SQL tests are passing. The other failures seem unrelated.

[dpebot]

/gcbrun

[JustinBeckwith]

@shubha-rajan thanks! Looks like it needs an npm run fix to address the lint issue.

[dpebot]

/gcbrun