more monkey business with the user guide and tests ...

SeasideREST load behavior has changed, now that #stable version of
Seaside was changed to 3.1 (used to be 3.0) ...

UserGuide is using SeasideREST as poster child for locking and I'm
inclined to only lock baselines ... locking is more useful (in concept)
for allowing users to control which repository is used and less useful
for controlling which version is being used ... controlling version is
important, but it is more likely that a user will be taking ownership
of a repository (where version matters) than simply letting the universe
control the definition of the version ... it is not easy for lock to
manage monticello repositories in the same way that it is used for
baselines (where the version represents the contents of a repository)