Adjusted to make it clearer about using require inline

In the wall, we have multiple require statements for middleware:
```javascript
	/**
	 * Express domain error handling. (must be the first middleware)
	 * @description This uses node domain api (http://nodejs.org/api/domain.html) to
	 * catch uncaught exceptions and allow the application to continue.
	 * @description It is 3rd party middleware (https://github.com/brianc/node-domain-middleware)
	 */
	app.use( require( 'express-domain-middleware' ) );

	// We want an app level route to handle 3rd party status checks
	// If /status is called, handle that here
	app.use( require( './middleware/healthCheck' ) );

	// SNS client to listen to SNS messages
	app.use( require( './middleware/notificationListener' ) );

	// Identify the brand we are on for this request & set some variables
	// Must happen first as all other routes use variables set here.
	app.use( require( './middleware/brandIdentify' ) );

	// Static routing (must come before configuration routing)
	app.use( require( './middleware/staticRouter' ) );
```

Looking at the coding guidelines, it would be counter-productive in this case to assign each middleware to a variable as it would consume unnecessary memory.

For this reason, I propose we change the guidelines so we only shift requires to the top when assigning to a variable.