Two factor authentication on front-end

When two factor authentication is enabled and in all plugins it is set to use it only in back-end then in front-end secret key field should be hidden in users component as in login module.
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_id=8103&tracker_item_id=33153
Update view.html.php
Fixed mod_finder JavaScript error

com_finder/autocompleter.js requires Mootools
[fix] Ignore System tests config file

This file is the config file for testing it should be ignored by the repo because is different in every machine
Improved loading JHtml::_('behavior.framework') of mod_finder
Make JEventDispatcher compatible with HHVM

According to HHVM inconsistencies guildline, "Under Zend PHP, foreach by value will modify the array's internal cursor under certain circumstances. Under HipHop VM, foreach by value will never modify the array's internal cursor.

Moving end() from above key() function to below it also make the code easier to understand as the behavior of foreach with array cursor is complicated to understand.
[#30197] class hide-phone for active numeric pagination items
Updating isis
make rssurl param required and validate to url
fixed typo in noframes header

Correct header name is X-Frame-Options not X-Frames-Options as stated in [the docs](https://developer.mozilla.org/en-US/docs/HTTP/X-Frame-Options)
fixed JModelForm::checkin()

Fixing issue described in [bug #30700](http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=30700), related to notices for unset properties of the $table object in JModelForm (libraries/legacy/model/form.php)
[#30929] fix JHtmlQuery::suggested()

Fixing issue described in [bug #30929](http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_id=8103&tracker_item_id=30929), related a case sensitive alternative search terms creation (components/com_finder/helpers/html/query.php)
Use jQuery for create captcha into plugin
Updating Config Front End Test File
Update TagManager0001Test.php

on line 117 the command was checking whether the tag was in row two but instead of that it was checking that if it was present in row 1.
on line 137 it was checking whether tag that was added its row number should be one but that's not necessary as if there exited some tags already then its row number would be accordingly as it should be but not 1. so now I am just checking here that its row number is greater or equal to 1.
Update TagManager0001Test.php
Update unit test for JForm
Update ConfigFrontEnd0001Test.php
Adding code for Page Object Messaging Edit Page
Implement Framework CLI output extension with b/c