Improve performance related to `cf.Field.autocylcic`

Now that we have #851 (Improve detection of cyclic axes), I realise that we no longer need to run cf.Field.autocyclic during cf.Field.set_construct, because autocyclic will get end up being run anyway, if required, whenever cf.Field.cyclic() is called.

This doesn't change any functionality, but will speed up the reading of remote datasets. Currently, even if you set cache=False to cf.read, set_construct ends up accessing the cyclic axis bounds values from the dataset, which can be slow.

Pushing the overhead of autocyclic to when cyclicity is actually needed makes sense because i) you may well not need that information in your workflow and ii) the overhead of the operation will likely make the autocyclic overhead not seem so bad.

Note that once autocyclic has been run once, it caches the values it need from disk, so is faster the next time.

Start by tracing cf.Field.set_construct and its interaction with cf.Field.autocyclic and cf.Field.cyclic. Remove the eager cyclicity work from set_construct while preserving the existing lazy behavior, then verify that cyclicity is still detected when cyclic() is called and that remote dataset reads avoid unnecessary bounds access.