MULE-7629: Fix test by resolving symbolic links when checking the original directory property.
Merge pull request #734 from mulesoft/MULE-7629

MULE-7629: Fix test by resolving symbolic links when checking the origin...
MULE-7632 - update jetty transport to use MessageProcessingMananger
MULE-7263 MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when http requests are proxied
Merge pull request #738 from vromero/dev/vromero/bug/MULE-7263

MULE-7263 MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when ...
Merge pull request #735 from mulesoft/MULE-7632

MULE-7632 - update jetty transport to use MessageProcessingMananger
MULE-7633 MuleBaseVariableResolverFactory cannot assume that nextFactory.getVariableResolver() will return null if variables doesn't exist.
Merge pull request #739 from mulesoft/MULE-7633

MULE-7633 MuleBaseVariableResolverFactory cannot assume that nextFactory...
Revert "MULE-7263 MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when http requests are proxied"

This reverts commit 830dd449485444cbf69875d2275c7f09f09f486e.
MULE-7631: CopyOnWriteCaseInsensitiveMap KeyIterator class implementation issue
Merge pull request #742 from mulesoft/MULE-7631

MULE-7631: CopyOnWriteCaseInsensitiveMap KeyIterator class implementatio...
MULE-7263 MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when http requests are proxied. Test fixed.
Merge pull request #743 from vromero/dev/vromero/bug/MULE-7263

MULE-7263 MULE_REMOTE_CLIENT_ADDRESS variable gets the wrong value when ...
MULE-6926: Fix flaky test
Merge pull request #744 from mulesoft/flaky_killer

MULE-6926: Fix flaky test
MULE-7636 changing MuleProcessController default timeout
Merge pull request #747 from mulesoft/MULE-7636

MULE-7636 changing MuleProcessController default timeout
Update mule-transports-http to tomcat 6+

mule-transports-http depends on tomcat 5.5.23 for cookie processing.
Upgraded to tomcat 6 version used by mule elsewhere using
${tomcatVersion}.  Tomcat moved this into coyote.  Verified working in
tomcat 6+.  Defaulted httpOnly to false in this instance since it was
not part of tomcat 5 and not part of cookie from commons-httpclient and
thus was naturally already false.  In tomcat 6, httpOnly is configurable
and default in tomcat 7+.  This seemed most appropriate way to get onto
tomcat 6+ as tomcat 5 is end of life and solved use case we had running
mule within tomcat 7 & 8.