Make Pro requests public by default

[RichardTaylor]

Currently there is a default position of a 3 month embargo on Pro requests.

I suggest making no embargo the default, and requiring the setting of an embargo to be something which needs to be done actively, this would promote the publication of requests and responses.

Issue raised having seen a Tweet by a Pro user who appears unsure about the embargo they have set:

I just started using their pro 'batch' functionality and I think they'll get published after 3 months.

https://twitter.com/librarieshacked/status/1447876576780161033

[garethrees]

A good place to note https://github.com/mysociety/whatdotheyknow-theme/issues/841.

[garethrees]

Also a good place to make clear https://github.com/mysociety/alaveteli/issues/6321.

[FOIMonkey]

+1 I keep nearly making embargoed requests by mistake. It'd be good to be able to set a default that applied to all my requests unless I said otherwise.

[garethrees]

Simplest thing to do here is change the default value of the select box and add more emphasis to the consequence of selecting a particular value:

We'd want this to coincide with an announcement on the dashboard, and possibly a blog post.

[garethrees]

Would need to consider interaction with https://github.com/mysociety/alaveteli/issues/7317. Just-created requests should have the same mechanics as just-published requests.