Mxml/intellisenseimprovement

As the commit description says:

- Added event completion support. Decided to make matches lookup more relaxed than the one in other IDEs.
- Added function type completion support.
- Added Inspectable metadata support. This required some global ActionScript metadata parsing improvements.

Regarding the first point: other IDEs just look for functions with a single argument that has a compatible event type, inside the current class. I look for all compatible functions (ie: functions with more than one argument where the others are not mandatory, functions where the first argument type is also Object or *, matching public and protected functions from parents...). Event handler creation is not supported at this moment.

About the third point: current FD metadata support is way incomplete (not that FD ever had more use for it anyway), as a lot of metadata is ignored and incorrectly appended to the file model while metadata can be defined for most object types. I only added Inspectable metadata support, so there are stil a lot of metadata tags not processed, but, again, they are not being used inside FD. To solve the second issue I extended MemberModel and added a MetaData property and when parsing source files I don't store the metadata in the model until we get what object type it supplements, for now, only functions and variables, although I haven't checked this: maybe after the big switch the current member is stored and metadata can be appended to anything as it should? at any rate, it's enough as it is right now.
But it's not the same thing, 'entry[0] + "=\"" + entry[1] + "\"" compiles into something similar to using StringBuilder for the whole thing. Using a string for the rawParam concatenation would cause copying around data unnecessarily. It's a small string, but in some codebases the loop may run thousands of times, and some metadata may indeed have more and larger strings. I don't think this is extreme optimization nor something along the lines, in my experience it's a normal block of code. Anyway, if you don't like it or don't feel it's ok you can change it, no problem with it myself.