Start on provisions for password-protected share rooms.

Elaborate model.composedUrl() to take an optional "bare" parameter.  When
passed, query strings are not included in the result.

Set it in most calls to do the removal most of the time, except for the
first use of "?auth_required_format=json".
Remove now-extra specific excision of the version_info query string - the
"bare" option is invoked to do the job.
Merge branch 'master' into issue-143-passworded-sharerooms
Continue weaving in provisions for password-pending share rooms.  We now
have entries for them that indicate their state in an informative way, and
a tap provision so tapping can go to a get-password form.  Still have to
hook up the form, and handling of its result.
Make BasicAuthManager more comprehensive, providing for use whether or not
the session is authenticated.  Provide more explicit control of setting and
resuming the credentials, and incorporate what was
AccountModel.getBasicAuth() as .getAccountBasicAuth().

It now seems to be working.

(Note for later: we need to move the "offline" notification out of the
model and into some view element, probably the LoginView.)
Equip PublicShareRoomModels with a sync that respects password requirement
and temporarily pushes a basic auth for it.

Hook in respect for password requirements and a form to fetch it.

This all now seems to work for getting the metadata of the share room, but
it doesn't provide for the fact that the folder and file contents are also
password protected of the contents of the share room.

I will aim, next, for a model prototype on which ShareRooms, Files, and
Folders can all be based.
Extract the password-protected item handling provisions from
PublicShareRoomModels and install it in an abstract prototype model and
collection, for basing various items that are going to need the feature.
(Only the model base prototype gets detection of password protection, since
the top-level share room, where the condition is uncertain, is a model.
Collections are always encountered as contents of an already identified
password-protected superior container.)

Weave the base into folder and file collections and models, and also into
versions, and adjust various views so that models and collections residing
within password protected share rooms all inherit the password.
Properly detect and handle invalid public share rooms password.
Add a facility to AccountModel for managing associations of public share
room passwords with the current account.  This will be used to retain share
room passwords over the extent of a login session.  (It could be extended
to retain passwords across logins and application sessions, using settings,
but that is not currently being implemented.)
Extend the provisions for password-protected entities to use the new
AccountModel.PubSharesPassManager to retain passwords within logins, and
from the non-authenticated state into logins.

Also, implement a functional interface to normalize getting and setting
passwords similarly across collections and models.
Use the new functional interface for getting and setting entity passwords.

Also, rectify the view finagling that's done after a valid password is
obtained, so that the share rooms root view still remains between the visit
into the passworded-shareroom's contents and the menu sheet.

That last part leaves a problem, where the share room root view is not
properly updated on resolution of the passworded-shareroom's metadata.  I'm
going to work on that next.
Improve the getShareRoomPasswordTemplate layout, and remove a debugging
initialize method left in FileModel.
Respect shareroom password-protection on for file download activities -
viewing, favorites, and intent sharing.
Unset 'password_required' once the model's metadata is returned, so the
item view renders properly.
Merge branch 'master' into issue-143-passworded-sharerooms

Conflicts:
	src/views/FilesView.js
Reconcile the FilesView.js merge conflict.

This is the only combination that seems to function correctly, though I'm
not sure why it's right.
Anything content object that can reside in a share room needs to be
"password-protected" aware, based on either the PasswordProtectedModelBase
or PasswordProtectedCollectionBase.  The FavoriteModel is such a case.  I
don't know whether or not there are others?
Some small tweaks

to hopefully bring Favorites and versions back in line with where they were before the password protected share rooms changes.
Fixed transition on auth and a typo
Fixes #171, fixes #186

An overly large looking commit with some test fixes as well as the main goal of tidying up the Public Share Rooms UX