Split jobs technical implementation from How-To SDK examples

[WhitWaldo]

Describe the issue
Typically when reading through Dapr documentation, the how-to docs will split out differences on a per-SDK basis. A .NET codetab will demonstrate how the goal is achieved in .NET, a Go codetab will do the same in Go, etc.

On the page referenced below, there's rich technical detail explaining how jobs work from a fundamental level leveraging both HTTP and gRPC with snippets of the Go SDK mixed in between.. but all this rich detail is hidden behind the Go codetab. Developers that approach the page and click on .NET (WIP) or other languages will only see the implementation details specific to their language.

URL of the docs
https://docs.dapr.io/developing-applications/building-blocks/jobs/howto-schedule-and-handle-triggered-jobs/

Expected content
It's a low priority, but I think the technical details on this page of how everything works in the background exclusive of the SDKs should be extracted to a dedicated page detailing it in a more code-agnostic manner such as how timers/reminders are detailed in the actor docs.

Additional context
N/A