Capx 88 | Required fields on mapper form

# Ready for review

* Adds required field validation to mappers
* Fixes a couple of bugs

Simply adding required to the form elements that are required causes errors in the form submission as it processes all fields as required when we only want a portion of the form. This is a problem with the way the form is generated to begin with but it is easier to work around it. Validation for required fields has to be on the validation hook. This is not a problem. The mapper form uses a theme_wrapper that replaces a field's label with the required asterix (*) with a preg_replace. This is kind of yucky and am open to suggestions on a better fix.
I just read the api.drupal.org docs for t(). From the page:

You should never use t() to translate variables, such as calling: t($text); 
, unless the text that the variable holds has been passed through t() elsewhere (e.g., $text is one of several translated literal strings in an array). It is especially important never to call
t($user_text); 
, where $user_text is some text that a user entered - doing that can lead to cross-site scripting and other security problems. However, you can use variable substitution in your string, to put variable text such as user names or link URLs into translated text.