Fixed verbose flag viewing with no taskname

Before, when executing view --verbose, the taskname would be read as
--verbose instead of the current task's name. This caused the sequence
file to not be found and the view command to behave differently then
from a view with no arguments that WOULD find the current task. So this
is now fixed.

There is no checking on the special case for the current task not
existing and there probably should be. This is not the bst strategy
especially since valgrind now reports a conditional jump which is
troublesome. Handling the view with no task name needs to be flushed out
a bit better and will come with a refactor.
Fixed whitespace issue in task name

Before trailing/leading whitespace would cause the task name to be
considered different. Which is not what we want. So added a nice trim
function I found on S.O. to tc-task and using it when we first resolve
the task name from the arguments.
Fixed a few errors, added a validation script

Fixed a few uninitalized value errors (there's still one though) and
added a validate script that simple does a bunch of command through
valgrind so I don't have to type them all out and try to remember which
commands might mess with one thing or another.

There is an irritating issue with this commit's version of view -v (no
task name) in that _find_current_task doesn't go to the sequence file
for information or perform calculations correctly, so the start time is
off as well as all other time calculations. It's rather strange because
it's only the verbose output that is incorrect.
Fixed _find_current_task and flag parsing

Changed the flag parsing to use continue again instead of stopping at a
'-' because breaking causes the task name to be blank, which when
switching to a new task results in the new task being a blank for the
name. Which is not what is desired from the command. The previous
version worked fine with start <task name> -s but not start -s <task
name> and let's face it: Semantically, -s should come before the task
name since you're switching to it.
Fixed Sequence numbers to increment

Fixed Sequence numbers to properly create themselves. This has to be
done during read otherwise we'd never have a '0' sequence to base our
timing off of.

Unfortunately, my last validation check ( start -s task2, where task2 is
the current task ) causes a bit of a problem because it causes two 0'th
sequence numbers in the sequence file. Silly thing. I'll have to look
into that.