BatchThreadPoolDescriptionResolver currently has some specialized handling for common thread pool attributes. We should be able to simplify it, considering the following:

• have it extend StandardResourceDescriptionResolver to inherit the handling for the usual stuff;
• see if we can change the attribute description property key prefix to avoid such special handling (avoid checking for if an attribute is contained in COMMON_ATTRIBUTE_NAMES).
• I suspect if we don't do anything special, and just use the default standard resolver from wildfly-core, we will get the attribute description from wildfly-core/threads, which should suffice. (batch-jberet subsystem LocalDescriptions do contain some specific description for thread-pool attributes that are different than the common ones).