tests - update test loading to fix deprecation warnings in Django 1.7

(Django 1.7 error for reference:
  tests\support\models.py:40: RemovedInDjango19Warning:
  Model class tests.support.models.SimpleCommon doesn't declare an explicit app_label and
  either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded.
  This will no longer be supported in Django 1.9.)
Python 2.6 import because Django 1.7 deprecates this backport
use `get_queryset` for Django 1.6+
deprecate `get_query_set` instead of removing it outright to be friendlier to older Djangos

When ArmSections 2.0 happens, we can use the previous method of defining `get_query_set` via a conditional
tests - refactor to test the template tag itself in use, not the Node implementation. Add a couple new scenarios as well.

We made the same change to ArmLayout in armstrong/armstrong.core.arm_layout#12
tests Django 1.7 - remove app loading warning

"RemovedInDjango19Warning: Model class tests.models.NewSection doesn't declare an explicit app_label and either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded."
more readable comment tags
Merge branch 'template_tag_test_refactor'
Merge branch 'get_queryset'
project management - use new-style, standard tags for easy deprecation feature searching
tests Django 1.7 - easier way to handle app loading warning

This reverts commit aad6399f4104286263fb7b2d29bc8a6de97b3f41.
Resolving these errors: "RemovedInDjango19Warning:
  Model class tests.support.models.SimpleCommon doesn't declare an explicit app_label and
  either isn't in an application in INSTALLED_APPS or else was imported before its application was loaded."
fix " RemovedInDjango19Warning: Loading the `url` tag from the `future` library". Also do a little code cleanup.

This isn't pretty but you can't variable load template tags so use an entirely duplicate template file.
explicitly declare MIDDLEWARE_CLASSES because the defaults change in Django 1.7. Add messages to INSTALLED_APPS because we use the Admin.
Merge branch 'django17_prep'

Conflicts:
	armstrong/core/arm_sections/templates/arm_sections/sections_menu.html
migrations - use South 1.0 and `south_migrations/` in prep for Django 1.7
migrations - add for Django 1.7
tests need migrations, yuck.

"django.db.migrations.state.InvalidBasesError: Cannot resolve bases for [<ModelState: 'support.CustomSection'>]
This can happen if you are inheriting models from an app with migrations (e.g. contrib.auth) in an app with no migrations."
changes, readme and metadata update