Add and document `queue` parameter in `blocks.load()`

[apolinario]

• I have searched to see if a similar issue already exists.

Is your feature request related to a problem? Please describe.
If a job is running, the gr.Load() adds its tasks to the queue, kind of ruining the goal of running code at startup.

Describe the solution you'd like
I would like to be able to do a queue=False for blocks.load() while still leave the queue active globally for the app, in the same way I can do it for .click() or .update() functions

[pngwn]

You can set queue=False on a per event basis:

blocks.load(fn, inputs, outputs, queue=False)

[pngwn]

I dont understand why this isn't documented though. https://www.gradio.app/docs/#blocks cc @aliabd

[aliabd]

The queue parameter in blocks.load() isn't documented because it's not defined as a parameter, but looks like it works through the kwargs. The docs pull from the docstrings and it isn't there.

The blocks.queue() method isn't documented because it the @document decorator above Blocks only has load in it. As opposed to Interface which has: launch, load, from_pipeline, integrate, and queue. Not really sure why we made that call.

Would be easy fix to document the queue method (and also the others?), but for the parameter in load we'd probably have to define it outside the kwargs.

[apolinario]

I don't think queue=False in the load component is working. I set it to False and it still shows me queue regardless

[pngwn]

Do you have a simple repro that we can look at?