Implement a more complex vendored file detecting

The improved detecting method allows to examine if a file vendored by
not only its name but also its content.
Add Bootstrap library to vendor_complex.yml
Add test coverage for Bootstrap files
Update vendor-related section in README
Do not reset options when calling highlight
Allow for linguist override token

If anywhere in the first 5 lines, the pattern `linguist-override:' is
found, the next token is taken to be the overriding interpreter or
language.
Add .t as a valid Perl/Perl6 file extension
Make an exception for 'perl6' in the shebang line
Add a bunch of Perl 6 sample files
Update samples.json
NewLisp language added with some heuristics.
Regenerate samples
Merge conflict fixed.
dramatically enhance colors for javascript and css
update improved javascript color in test_language
Update vendor.yml

I have a C# repository containing C# libraries and an ASP.NET MVC project and the repository is marked as Javascript language. It seems that the problem is a NuGet package called Globalize. It adds 350 javascript to the folder "globalize/cultures" and with the pattern "globalize.culture.*.js". These files contain culture settings for each supported culture.

This package can be located here: http://www.nuget.org/packages/jquery-globalize/

This is my repository: https://github.com/Appverse/appverse-net

I have added this new exception to the file:
# Globalize NuGet package. Ignore the 350 javascript files containing culture settings
- (^|/)globalize/cultures/globalize.culture.*.js$
Add misclassified Prolog samples

These two files are incorrectly classified as Perl.  They should be
classified as Prolog.  There are many distinctive tokens in each file
which clearly differentiate between Perl and Prolog.
Trimmed white space.
Added Stata extensions.
Added .ado and .sthlp samples for Stata.

The author of this message, mwhite-IPA, is the source of these samples.