Consolidate SDK Docs into the main Docs repo

[marcduiker]

The docs for the Dapr SDKs live in their respective SDK GitHub repositories. The thought behind this was to make it easy for SDK contributors/maintainers to add new docs when they add new features. In reality, docs are frequently still an afterthought and are hardly ever in the same PR as the code changes.

Having the SDK docs is their separate repos also comes with some downsides:

1. It's time consuming to preview & test SDK docs due to the current submodule approach in the main Docs.
2. SDK docs frequently contain formatting issues which breaks the Hugo build.
3. There are many variations in the SDK docs since they each live in their silo and it's too much effort to see how another language written their docs.

I'm proposing to move all the SDK (and Pluggable Component) docs into the main docs. This will allow all SDK maintainers to preview/test their docs easily and it will help align the structure of all SDK docs.

Once the SDK docs migration of is done, the only submodule that remains is the Chinese translation of the docs.

• .NET SDK Move .NET SDK docs & pluggable components into main docs #4945
• Java SDK Move Java SDK docs into main docs repo and remove submodule #4946
• Go SDK Move Go SDK docs & pluggable component docs into main Docs & remove go sdk submodule #4951
• Go Pluggable Components SDK Move Go SDK docs & pluggable component docs into main Docs & remove go sdk submodule #4951
• Python SDK Add Python SDK docs and remove Python SDK submodule #4949
• JS SDK Move JS SDK docs to main docs repo and remove js submodule #4950
• Rust SDK Move Rust SDK docs and remove submodule #4953
• PHP SDK Move PHP SDK docs into main Docs & remove PHP SDK submodule #4952

[JoshVanL]

+1

[mikeee]

+1

Docs are currently too unwieldy, going untested until the submodule reference is updated

[WhitWaldo]

+1 Let me know when it's safe to delete the submodule from the SDK repos.