Have Behavior Names in Properties equal the Behavior classname as convention.

As we develop more behaviors, there is a chance (however remote) that somebody's characteristic's name would collide with an existing implementation. This could easily be solved if the we changed org.picocontainer.Characteristics constants for the "_*" attributes to be classnames.

Example:

Current:
_CACHE = "cache";

Proposed:
_CACHE= "org.picocontainer.behaviors.Caching"

I was going to suggest _CACHE=Caching.class.getName(), but that method wouldn't scale to Gems where Java would try to link optional classes that didn't have everything available on the classpath. For example, Slf4jComponentMonitor.class would throw a NoClassDefFoundError if Slf4j wasn't on the classpath.