Fixed many of the "post 1.3 ui revamp"-issues that were simple to fix.

 * firstuse
     * "Please stop the framework" => "Unable to start the Pipeline engine"
         * everywhere: rename "Pipeline framework" into "Pipeline engine"
         * "a running instance of the..." => "a conflicting running instance..."
     * "Create admin user" => "Configure Administrative Account"
         * "This seems to be is the first time"
         * "please fill the form to ... *configure* the administrative account for this website"
         * remove the horizontal line
         * "Please repeat your passwork again" => remove "again"
         * button: "Save and continue"
     * "Set the Pipeline 2 WS endpoint" => "Connect to the Pipeline 2 Web API"
         * everywhere replace "Web Service" by "Web API"
         * 2nd informative paragraph: make it an alert-info and move it as the last paragraph before the form
         * "You may skip this step now and change the address in the administrative settings later; however you will not be able to use any of the Pipeline 2 features until the Web API connection is configured. If you have not yet installed the Pipeline 2 engine, please download and install the latest version from the DAISY Pipeline 2 homepage (link this latter text to the web site)."
         * buttons => "Save and Continue" / "Skip Configuration"
         * alert-info: "The authentication ID and secret token were configured during the installation of the Pipeline 2 engine. To learn more about Pipeline 2's Web API authentication, please refer to the Pipeline 2 User Guide (link)."
         * rename "secret text" into "secret token".
     * Upload dir page
         * altert-info "Depending on the usage (especially when producing audio books) the file storage area may grow large. Please make sure that yo have enough free space on your file system."
 * Welcome page
     * only keep the paragraph describing the Pipeline project.
     * Embed the links in the target words.
     * Added centered primary button: "Get Started"
 * Scripts page
     * "Unable to communicate with..." add a paragraph "Please check the configuration  of the Pipeline 2 engine in the administrative settings."
         * add a subtitle "Loading..."
         * move the spinning wheel outside of the box or replace it with "attempting to connect to the framework."
 * Login page
     * use a page heading for "sign in"
     * move the "forgot password" as a new line between the form and the OK button.
     * group the "Login" and "Try it out as Guest" buttons together, centered, separated with "or"
 * "Scripts" page becomes "Create Job" page ("+" icon)
 * Job configuration page
     * remove the "File" field label and center the upload button ; rename the button to "Upload Files".
     * move the helper text to a collapsible area accessed via a "question mark" link
     * separate required and advanced options in two field sets, the latter with the legend "Optional parameters".
     * the optional parameters are a collapsible area, the "Show" toggle button on the side of the legend text.
     * rename "Available Files" into "Uploaded Files"
     * on the "Add"/"remove"/"Move up"/"Move down" buttons, delete the text, use bigger arrows, add an alt text.
     * Move the link to the script page to a "Online Documentation" link below the script heading, with an icon showing it's an external link.
 * "Jobs" list page
     * use normal "greyed" text for the "There are no jobs" info.
     * add a descriptive text "Displaying jobs for ..."
     * the first column displays "$JOB_NAME ($SCRIPT_NICE_NAME) <br/> muted ID."
     * use fuzzy dates ("10 min ago", "Yesterday at 5:03"), the exact canonical date is displayed in a new line as "muted" text.
     * new column "Results" on the right of the "Jobs" column with the green "Results" download button for DONE jobs with result, nothing for DONE jobs with no output.
     * the status column is moved as the first column, use a colored icon: green tick for DONE, red exclamation point for error, unclosed circle with arrow for running, and three dots icons for idle. The column itself has an information sign as a heading, with the "Status" alt text. Icons have both alt text and title tooltips.
 * Settings page
     * make each section a tab, hide non-selected tabs
     * rename "branding" into "Appearance"
     * rename "Jobs cleanup" into "Maintenance"
     * rename "OK, looks good" into "Save Settings"
     * "User & Permissions"
         * rename buttons into "Save"/"Clear"/"Delete User"
     * "Appearance" section
         * rename "title" into "Application Title"
         * update the about page title according to the application title
     * Guest settings (these are a bit off from the guest settings discussed in Madrid; this is a compromise to be able to get a version out without implementing the public user just yet)
         * moved the public/guest/authenticated mode selection to the "Global" section
         * renamed "Save changes" into "Save"
         * using a distinct icon for the guest account (whether or not it looks good is up for discussion though)
         * remove the "Show Guest Name" setting
         * removed e-mail box. Instead, it always shows in guest mode (unless emails are not configured) and otherwise never
     * Global settings
         * rename "Global Permissions" into "General settings".
         * "hide advanced options" becomes "Show Optional parameters" (yes|no) with description "Automatically expand optional parameters in the job creation screen".
 * Job summary page
     * Heading "Job Summary" newline $Job_Nice_Name newline "Show Details"
     * The "show details" text is smaller than the default heading size, has a chevron or plus button and is used to expand a collapsible area containing the job details.
     * Collapsible area containing the job's detailed info
         * Job: nice name
         * job ID (muted)
         * Running "script name"
         * Created 4 years ago
         * Started 2 years ago
         * Finished Yesterday
     * status
         * displayed in the hero unit (as currently done). The possible headings are "Success" (@class="text-success") | "Running..." (@class="text-info") | "Queued" (@class="text-muted") | "Failed" (@class="text-error").
     * Execution Log
         * The "Messages" heading is renamed into "Execution Log"
         * move the "Detailed Log" button below the "Execution Log" heading and rename it into "Download Detailed Log" ; makes it a download button to get the full log text file (containing the same content as the "Error Report" button that we show in the failed state).
         * output all the messages in the same block. (TODO: get feedback from mailinglist if this looks good or not)
         * style the line numbers with smaller font size and @class="muted", or use the prettify.css classes (@class="linenums")
     * Removed the "Other Output" section

Updated to Twitter Bootstrap v2.2.1
 * note: in bootstrap.css and bootstrap.min.css, "-webkit-transform: translate3d(0, 0, 0);" is commented out due to a Chrome bug: https://github.com/twitter/bootstrap/issues/4319