Service invocation supports passing of query strings/fragments in URL

[WhitWaldo]

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

• [X] Commits are signed with Developer Certificate of Origin (DCO - learn more)
• [X] Read the contribution guide
• [N/A] Commands include options for Linux, MacOS, and Windows within codetabs
• [N/A] New file and folder names are globally unique
• [N/A] Page references use shortcodes instead of markdown or URL links
• [N/A] Images use HTML style and have alternative text
• [N/A] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:

Description

This PR seeks to supplement the service invocation documentation to clarify that a query string and fragment can be passed within the URL and Dapr will pass it through unchanged. I couldn't find this documentation otherwise documented anywhere except as a single test case in the .NET SDK

Issue reference

https://github.com/dapr/dotnet-sdk/issues/1303

[WhitWaldo]

@hhunter-ms This PR has no dependency on the C# SDK PR I also created this morning as it's just sharing general guidance around the fact that the capability is there by default (where it's not presently called out).