DEVPROD-13512: Disable task generation in Genny.

[johndaniels]

We are switching over to using manually maintained files based in the DSI repo to run all Genny tasks. This removes any task generation functionality so that it doesn't cause confusion

[SimonEismann]

Let's use caution blocks here that should be harder to miss.

[johndaniels]

@SimonEismann This is the way to do admonitions in the Pine devprod docs, so it will be more visible there.

[SimonEismann]

Pine also supports notes now:
https://docs.devprod.prod.corp.mongodb.com/performance/profiling_workflow/#heap-profiling-heaptrack

But I can see just doing the thing that looks good in Pine as well.

[johndaniels]

😱

[SimonEismann]

As discussed at the onsite during the perf collab session, this is a good idea because the genny tasks are no longer expected to change much and we've learned the painful lesson that having evergreen configurations spread across multiple repos is hard to work with.

I would like to see the AutoRun blocks commented out in all workloads, with a corresponding comment explaining that it's deprecated. If possible, checking if the test defintion has an AutoRun block and failing immediately would provide a safe guard for any newly written tests. If the latter makes sense depends on how much work it would be.

[PyGeek03]

I would like to see the AutoRun blocks commented out in all workloads, with a corresponding comment explaining that it's deprecated. If possible, checking if the test defintion has an AutoRun block and failing immediately would provide a safe guard for any newly written tests. If the latter makes sense depends on how much work it would be.

Initially I thought this is a good thing to do in this PR as well. However, as mentioned in this PR here, AutoRun blocks are kept for backward compatibility with older older versions of the mongo repository. Do you think backward compatibility would be an obstacle for removing AutoRun blocks? Also, there's some Genny workload YML files in the 10gen/PrivateWorkloads repo with AutoRun blocks as well, should they be removed too?

[PyGeek03]

So happy to see Genny autotask going away, thank you team!

[PyGeek03]

I think it would be nice to modify the header to include the deprecation as well:

Suggested change

	### What is AutoRun?
	### What was AutoRun?

[johndaniels]

I actually have a separate change on my machine to delete AutoRun blocks that I can apply whenever. I didn't want to muddy this PR with it.

[johndaniels]

I would like to see the AutoRun blocks commented out in all workloads, with a corresponding comment explaining that it's deprecated. If possible, checking if the test defintion has an AutoRun block and failing immediately would provide a safe guard for any newly written tests. If the latter makes sense depends on how much work it would be.

@SimonEismann per the above comment I have a followup PR that replaces all the autorun blocks with HasTasks (since we use the presence of AutoRun to determine if there is likely a linkeable task). I wanted to keep the big change separate from the more focussed changes

@PyGeek03 I think this change is already backwards incompatible with any PR that does task generation.

This seems fine... it would only apply when using the latest version of Genny from an old version of Mongo and the workaround would be to mannually add the genny task info you want into DSI. I can add the workaround info to https://docs.google.com/document/d/1YzzrmKgIcpLG-60IdejYD4pxJzUQR-dy_nrrBgnLbBA/edit?tab=t.0 if that makes sense to do.