Repair GH repo page url view only to point to master as committed original in #89

Applies to #200

* I currently see no advantage of pointing the view url to the current `tree/HEAD` when clicking the url to go to GH during the import process. I do however see a disadvantage of not being able to traverse up their breadcrumb list and being locked into a specific commit hash
* Since the import process is probably dependent upon `/tree/HEAD` now leaving that alone
* Add `target="_blank"` to this url since we do this anyways with multiple entries and keeps that window/tab open for importing after checking with GH
* Fix white space issue with optional target after POST routine returns
Remove straggling trailing commas in objects

* This is considered bad form and could eventually break this controller if V8 updates to strict mode.
* Think I got all of them on a manual survey of this controller.

Applies to #200 and should be clarified in #19
Option 2 for #204

* Create another object for mustache to correctly show GH target url if percent is used in `dir` or `filename`
* Alter view page mustache usage to match

Applies to #200 and https://github.com/OpenUserJs/OpenUserJS.org/issues/200#issuecomment-47057757
Backout master reference since GH allows different HEADS... rarely used but I have seen a few ppl do this.

Applies to #200 and #204
Further things for #204

* Use `encodeComponent` as per @Zren recommendation
* Use `repo.default_branch` to eventually be redirected to `blob/master` url

NOTE: May need default_branch to be encoded I think... have to commit this to check out my other repo and test

Applies to #200
More for #204

* Create minimal `repoAsEncoded`
* Use `repoAsEncoded` in view page

Applies to #200
Remove the BOM from the only file I have found it on.

If running Linux a good recursive method for detecting these is:

``` sh-session
$ find . -type f -print0 | xargs -0r awk '/^\xEF\xBB\xBF/ {print FILENAME} {nextfile}'
```

Applies to #200 and #198
`@copyright` handling

Applies to #209
Uppercase according to [IETF](http://tools.ietf.org/html/rfc3629#section-4)

Applies to #198 and #200

**NOTE**
* Why is there a `defer` flag for ace? Could be related to #148
* Currently ignoring `./public/js`
Merge pull request #213 from Martii/Issue-19StyleGuide

Some strong emphasis and additions/clarifications for #19
Merge pull request #211 from Martii/Issue-209atCopyrightFixes

`@copyright` handling

Merging so working on this twice doesn't happen depending on the results of #208.. .going to automerge another one with "flux" on `@collaborator` and `@author` on the Add Scripts page... need this one finalized though.
Move `@author` and `@collaborator` to bottom and denote possibly changing

* Some of the classes don't exist yet that are used and I did change it from `active` to `inactive` just to denote the eventual styling.

Applies to #208
Merge pull request #214 from Martii/docForFluxOfCollaboratorMethodology

Move `@author` and `@collaborator` to bottom and denote possibly changin...
Merge pull request #204 from Martii/repairUrlToGHMaster

Repair GH repo page url view only to point to master as committed originally...
Merge pull request #206 from Martii/BOMRemoval

Remove the BOM from the only file I have found it on.
Merge pull request #212 from Martii/toUpperUTF-8

Uppercase according to [IETF](http://tools.ietf.org/html/rfc3629#section-4)
Use "12 Mar" if relative date is >7days. "Feb '13" if not this year.
Merge pull request #215 from Zren/dates

Use an actual date on relative timestamps if older than 7days (the way I had it before, so you know I'm going to merge this)
Reverse all handled keys except `@supportURL`

* Use `unshift` to keep code simpler

Applies to #210
Reverse multiple handled key order and match code point to display points

* Last value is primary for all multiple shown keys in script source but display reversed. Using last as primary will save us headaches down the line.
* `supportURL` is only using last one in our `script.support` so no need to mess with that.

Closes #210