fix(ci): updated permissioning and versioning in GitHub Actions

[VRamakrishna]

• Fixes the failing deploy_docs.yaml action by adding token with appropriate permissioning.
• Pegs the protoc-gen-go-grpc version in the relevant actions to v1.4.0 to match what's written in the documentation (this avoids test network setup failures when running integration tests.)
• Removed dead code from the Weaver Corda sample application.
• Made mkdocs publish URL customizable by owner.

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[VRamakrishna]

FYI, I tested and the docs publish works in my fork.

[petermetz]

@VRamakrishna Please include the full information you have in the PR description in the commit message as well!

[VRamakrishna]

@petermetz Done.