Simple refactoring transformations without logic change

Actual flow of code is somehow becoming visible. I wonder how things got this bad....

Extracted method and got rid of outer label/continue statement

Bug 419314 - Allow to determine whether artifact/metadata resolution exceptions have been played back from the error cache

Added isFromCache() property to (Artifact|Metadata)TransferException

Made PathRecordingDependencyVisitor stop traversal upon cycle entry, also added test to verify NearestVersionSelector's usage of PathRecordingDependencyVisitor does not suffer from cycle-related issues either

Made DefaultUpdateCheckManager support aether.updateCheckManager.sessionState configuration property to bypass or disable in-session state

Added JreProxySelector to aether-util

Made HttpTransporter check for WebDAV-capable server and issue MKCOL requests as needed to create missing parent directories before the actual PUT

Made DefaultInstaller bail out with exception if source and destination of install operation are equal

Wrapping a stream that is read/written in large chunks with BufferedXXStream is
useless, causing excessive copying of data and reduced performance

Wrapping a FileOutputStream that is written in chunks of 32K with an 8K BufferedOutputStram
produces only hot air and no performance gain. (Actually a perf. reduction)

Bug 413867 - Concurrent artifact resolution using same repo session (data) in combination with enhanced local repo can fail sporadically

Fixed interaction between DefaultArtifactResolver and DefaultUpdateCheckManager to ensure download requests for unavailable artifacts are not suppressed unless a resolution error has been cached

Bug 413880 - Artifacts get downloaded from every configured remote repository if resolution error caching is completely disabled

Undid bad refactoring from e5086685 and maintained one resolved flag per artifact, not per resolution item

Properly handled edge case of concurrent attempt to resume download where later thread uses bad remote repository and hence should fail resolution as opposed to consume the result of the first thread

Made SafeTransferListener also handle linkage errors caused by potential API incompatibilities similar to DefaultRepositoryEventDispatcher