fix(deps): update dependency @grpc/proto-loader to ^0.7.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@grpc/proto-loader (source)	^0.5.0 -> ^0.7.0

---

Release Notes

grpc/grpc-node (@​grpc/proto-loader)

v0.7.13: @​grpc/proto-loader 0.7.13

Compare Source

• Include method options in method definition objects (#​2711 contributed by @​n0v1)
• Avoid generating duplicate TypeScript method declarations in some cases (#​2717)
• Update Protobuf.js dependency to a newer version (#​2731)

v0.7.12: @​grpc/proto-loader 0.7.12

Compare Source

• Revert "Use a .ts extension in import statements in generated TypeScript files" (#​2699)

v0.7.11: @​grpc/proto-loader 0.7.11

Compare Source

• Use a .ts extension in import statements in generated TypeScript files (#​2693 contributed by @​atjn)

v0.7.10: @​grpc/proto-loader 0.7.10

Compare Source

• Allow the grpcLib option to be omitted in the type generator, to generate implementation-agnostic code (#​2573)

v0.7.9: @​grpc/proto-loader 0.7.9

Compare Source

• Update long dependency to match protobufjs (#​2504 contributed by @​haines)

v0.7.8

Compare Source

v0.7.7: @​grpc/proto-loader 0.7.7

Compare Source

• Update yargs dependency to 17.x (#​2437)

v0.7.6: @​grpc/proto-loader 0.7.6

Compare Source

• Avoid importing Long in files that don't use it (#​2370 contributed by @​install)

v0.7.5: @​grpc/proto-loader 0.7.5

Compare Source

• Include @deprecated annotations in generated comments if the includeComments option is set (#​2357 contributed by @​danielronnkvist)

v0.7.4: @​grpc/proto-loader 0.7.4

Compare Source

• Support nominal typing with type branding (#​2281 contributed by @​LunaTK)

v0.7.3: @​grpc/proto-loader 0.7.3

Compare Source

• Add message class name template options to TypeScript generator (#​2183 contributed by @​install)

v0.7.2: @​grpc/proto-loader 0.7.2

Compare Source

• Revert upgrade of long dependency (#​2197)

v0.7.1: @​grpc/proto-loader 0.7.1

• Update long dependency to version 5 (#​2192)

v0.6.13: @​grpc/proto-loader 0.6.13

Compare Source

• bump protobufjs dependency to "^6.11.3" (#​2131 contributed by @​ocofaigh)

v0.6.12: @​grpc/proto-loader 0.6.12

Compare Source

• Revert long dependency to 4.x (#​2114)

v0.6.11: @​grpc/proto-loader 0.6.11

Compare Source

• Broaden dependency on long to 4.x or 5.x (#​2112)

v0.6.10: @​grpc/proto-loader 0.6.10

Compare Source

• Update the dependency on the long library to version 5 to fix some TypeScript type compatibility issues (#​2110)

v0.6.9: @​grpc/proto-loader 0.6.9

Compare Source

• Decrease dependency to yargs 16 for compatibility with Node <12 (#​2010)

v0.6.8: @​grpc/proto-loader 0.6.8

• Use predefined types for callback functions in generated code (#​1967)
• Improve consistency of generated code formatting (#​1981)
• Update dependency on yargs (#​2006)

v0.6.6: @​grpc/proto-loader 0.6.6

Compare Source

• Make serializer functions reject array arguments (#​1940)

v0.6.5: @​grpc/proto-loader 0.6.5

Compare Source

• Avoid generating method names in service client interface definitions that conflict with method names in the base Client class (#​1897)

v0.6.4: @​grpc/proto-loader 0.6.4

Compare Source

• Fix a bug that caused some imports to be incorrectly omitted in generated code (#​1832 contributed by @​mtlewis)

v0.6.3: @​grpc/proto-loader 0.6.3

Compare Source

• Remove unused imports in the generated code (#​1826 contributed by @​mtlewis, @​install, and @​joeporpeglia)

v0.6.2: @​grpc/proto-loader 0.6.2

Compare Source

• Fix auto-generated service definition (#​1778 contributed by @​EduardoLaranjo)

v0.6.1: @​grpc/proto-loader 0.6.1

Compare Source

• Generate TypeScript types showing that unset message field values can be null instead of undefined in some cases (#​1744)
• Generate more detailed TypeScript types for service definition objects (#​1745)

v0.6.0: @​grpc/proto-loader 0.6.0

Compare Source

• Add a generator for TypeScript types for the objects created by this library (#​1474)
• Add fromJSON method for loading types represented as JSON objects (#​1713 contributed by @​SOVLOOKUP)

---

Configuration

📅 Schedule: Branch creation - "after 9am and before 3pm" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 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 was generated by Mend Renovate. View the repository job log.

[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.

[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.

[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.

[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.