Split, credit, patch vendor libraries

[rdalverny]

We have several libraries bundled in the trunk for now:

• PEAR (list to determine) - several licenses such as PHP License, Apache License, LGPL, BSD style, MIT License
• ADODB - dual licensed using BSD and LGPL
• Smarty - LGPL
• HMTLPurifier - LGPL 2.1
• spyc - MIT License
• simpletest - LGPL 2.1

Plus:

• mootools - MIT-style
• SWFObject - MIT License
• UFO - LGPL 2.1
• growl.js, sprintf.js and star_rating.js - no license

Some have patches (to prevent notices or to fix/enhance bits here and there).

So:

• we have the vendor/* branches to populate with the last up-to-date release
• move our customized libraries in vendor/*/current
• try to isolate our patches
• upgrade vendor/*/current
• apply/discard/update our patches - send them upstream
• if we have an untouched vendor branch, discard it completely and put it as an external requirement for Turbulences
• when releasing an archive, bundle these libraries as an option if possible or modify the codebase so it can check if correct libraries/versions are available.

See  http://svnbook.red-bean.com/en/1.4/svn.advanced.vendorbr.html.