Fix workload targets and max runtimes in docs

[runame]

Fixes #660 and #684.

@priyakasimbeg I noticed that we don't have a shared parent class for the librispeech deepspeech workloads and specify the targets, max runtime, and other properties twice -- once for Jax and once for PyTorch. Is there any reason for that? If not we should probably create a separate workload parent class. Otherwise it is easy to introduce a bug by accidentally making these values inconsistent.

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[priyakasimbeg]

Hi Runa,
Thanks a ton for working on this.

I noticed that we don't have a shared parent class for the Librispeech DeepSpeech workloads and specify the targets, max runtime, and other properties twice -- once for Jax and once for PyTorch. Is there any reason for that?

Right they inherit from the conformer JAX and PyTorch workloads to reuse the input pipeline and other methods. We actually had a bug until a few months ago where the DeepSpeech workloads were inheriting all the properties from the conformer workloads (including targets). The targets and runtimes were specified in a Librispeech DeepSpeech parent workload that was not being used so I removed it (#526).
At the time I took a stab at separating DeepSpeech from Conformer but it quickly turned into a mess with a large amount of duplicate code.
This is definitely a good thing to fix at some point in the future but I don't think we want to go down that rabbit hole right now.