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.
Well, the amount of parameters rawParams may have may justify it, what if there is some crazy custom metadata with tons of parameters, or with some huge strings? Anyway, I also said in my first comment it doesn't matter much. For me the subject of the discussion is that 'entry[0] + "=\"" + entry[1] + "\""' line doesn't damage or modify the StringBuilder operation or characteristics at all.

Already told it, I don't care about that piece of code, you can change it, or if you want me to change it I'll do so, although won't be able till tomorrow, I'm on a different PC right now.

The thing that matters is that this is an improvement, although that if (entry.Length != 2) continue; line skips metadatas that don't have a key-value property (I didn't think about how to store them in a Dictionary, maybe repeating the value for both things, or using some special const for the key).

The commit can be helpful for other developers, eg: somebody that would like to work on a visual editor could now get extra info about available attributes in order to categorize them or get possible values, and users of that editor could extend it through custom metadatas that define editors for custom data types and the like.