WildFly should not identify itself as 'WildFly Full'

In the 'starting', 'started in' messages and in the root management resource 'product-name' attribute value, a WildFly installation provisioned from the 'wildfly' feature pack identifies itself as 'WildFly Full'.

This should just be 'WildFly'. 'WildFly Full' isn't really a thing. The 'full' term has had various uses, e.g. contrasting with WildFly Core or contrasting with something that only used the wildfly-ee feature pack, but we shouldn't make that a formal part of how the server identifies itself.

Note that provisioning solely from the 'wildfly-ee' feature pack results in the server identifying as 'WildFly EE' which is ok. If you're not using the 'wildfly' feature pack you're not getting an installation that's the same as what we generally refer to as 'WildFly'.