data-* attributes changed names

Changed names to avoid possible conflicts
data-intro is now data-intro-text
data-step is now data-intro-step
data-position is now data-intro-position
Create introJQHelper.js

Through JQuery this adds a few simple "features" to the into.js first you can attach a class introStart to any clickable object. This class will start an intro based on a few settings on that button.

First setting is data-intro-next-href which will make the intro continue on to another page when finished.
i.e. <a class="introStart" href="#" data-intro-next-href="http://google.com">Intro</a>

Second allows you to specify page sections to run the intro on (using normal JQ style selectors) if not set it will run an intro on the whole page.
i.e. <a class="introStart" href="#" data-intro-section=".introClass">Tour</a>

Third allows you to specify page sections to continue the intro on (using normal JQ style selectors) if for some reason you want to break it up.
i.e. <a class="introStart" href="#" data-intro-section=".introClass" data-intro-section="#introNext">Tour</a>
tweaked README spacing
Merge remote-tracking branch 'remotes/usablica-original/master'

Conflicts:
	README.md
Merge remote-tracking branch 'remotes/vipero07/master'

Conflicts:
	intro.js
gitignore editor bak files, etc. + gitattributes to ensure UNIX LF for all sourcefiles anywhere
updated library files
Merge remote-tracking branch 'remotes/usablica-original/master'

Conflicts:
	intro.js
Merge tag 'v0.6.0'

v0.6.0

Conflicts:
	README.md
	intro.js
	minified/intro.min.js
- upgraded to Boostrap 3.0.3 NOT MINIFIED (minified files screw you up when doing global search through libraries...)

- killed the minified files (dev's don't need them and production servers/sites have their own minification processes in place)

- fixed the merged files to all adhere to the non-colliding `data-` naming standard: all Intro.JS data- DOM attributes start with `data-intro-`

- re-centered the Intro.JS tooltip number in the red circle.
properly correct the CSS to show the red number per tooltip: now the red circle is bigger and fits each number easily.
feature: provide role-specific intro texts: site visitors may have different roles and require different assistance and thus feature makes this possible, including switching roles 'live' in-app.

Two examples are included which showcase the augmented behaviour.
- documented the goToStep() API a bit more, mentioning that the step number is '1 based'

- introduced the getCurrentStep() API so user code can store the current IntroJS state when the overlay is clicked or the introduction is aborted another way, to be continued at a later time.

- bumped version to 0.6.1
initial prepwork phase 1 for preconditioning and tracking introduction state.
complete the work done in SHA-1: 21c50cdb36879b1f6884ad27f49893330fe525cf: all introJS attributes are `data-intro-` PREFIXED -- which means that the old `data-intro` DOM attribute is now named `data-intro-text`
further data-intro- fixes lingering...
be robust against complex rerendering/updating of the addressed DOM node by any application user code: prevent crash when introJS class tweak is already gone.
Revert "properly correct the CSS to show the red number per tooltip: now the red circle is bigger and fits each number easily."

This reverts commit 6e64d8c87a3062c51c81b15fb76b276275efb25e.

That commit changed the red number styling to suit my browsers but for some unidentified reason all browsers were rendering incorrectly - the next night, after a complete machine crash (hardware freeze) and reboot the edited styling is wrong, as it was on a freind's machine (OS/X) -- for which I had no explanation at the time. Apparently something very odd happened on the local dev box there.
- added preliminary example to showcase custom actions when overlay is clicked.

- user callbacks introExitCallback and introCompleteCallback now are called with a 'reason' parameter, which is an object containing information about which action/event triggered the callback.

- always call _exitIntro() AFTER the user callbacks have been invoked: hence _exitIntro is the very last action performed by IntroJS when the demonstration terminates.