Signed-off-by: Malf Furious <m@lfurio.us>

Some form handlers use the current logged in user (user::getCurrent()),
however do so without asserting that we are _actually_ logged in.  This
is probably due to that fact that index.php (usually) catches all page
requests that are logged out and diverts control before any other handler
can be invoked.  But a few handlers sneak through the cracks.

In the future, the app will be better about supportting logged out
browsing, the alpha was not written with this in the forground.

Signed-off-by: Malf Furious <m@lfurio.us>

POSTs to the dm-issue-add form are handled by this new handler.  Pad
data is passed via the form, we create the new issue in the pad's first
stage, crediting the current logged in user.  New issue is unassigned.

I call `location()` at the bottom, since not doing so leaves the page in
a weird state.  The reason being that most of the page rendering logic
operates off of the 'pageObj', which is instanciated and assigned prior
to the invocation of this handler.  This is to be fleshed-out during the
v0.2-v0.3 development iteration.

Signed-off-by: Malf Furious <m@lfurio.us>

As a convenience, I'm adding a basic set of stages to new pads.  These
stages are "To Do", "In Progress" ('Done' being closed issues).  This
implements a very simple workflow for new pads.