Modify xdmod source for php7 compatibility

[jsperhac]

Description

Fixed up xdmod core source based on the output of php7cc version compatibility checker (https:/sstalle/php7cc). This provided an opportunity to delete some woefully dated source code that used deprecated syntax and packages.

This is necessarily a mixed bag of changes, consisting of code deletions, class renaming, deletion of unused database tables, and adjustment of syntax in the test harness.

Refer to pull requests https:/ubccr/xdmod-xsede/pull/29 and ubccr/xdmod-appkernels#18 for associated changes for php7 compatibility

As spelled out in the original commit remarks:

• Renamed the open XDMoD shredded ingestor Resource class, and fixed call to class (reserved word)
• Replaced split() with explode() in XdmodTestHelper
• Removed unused class Glossary.php and unused moddb tables Glossary and GlossaryAliases
• Removed unused source controllers/ui_data/repogen_sites.php
• Removed unused source libraries/network.php
• Removed unused tokenResolver() from libraries/utilities.php
• Removed old, unused controller code associated with user_profile

Motivation and Context

This PR helps prepare xdmod for a migration to a newer PHP version, and provides the opportunity to prune some unused and outdated code.

Tests performed

All existing integration and unit tests were run without incident. Where coverage is limited (e.g. user profile), manual testing was done to ensure no behavioral changes were introduced.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project as found in the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[jtpalmer]

Please add this to the bottom of the file:

INSERT INTO `schema_version_history` VALUES ('moddb', '6.7.0', NOW(), 'upgraded', 'N/A');

Also, please update the schema version in db/data/moddb.sql.

The schema versions aren't used for anything at this time, but might as well keep updating them until we decide if we want to get rid of them.