This fixes the following compiler warning that is reported in Travis builds:
```
/home/travis/build/apache/activemq-artemis/artemis-core-client/src/main/java/org/apache/activemq/artemis/core/protocol/core/impl/wireformat/FederationStreamConnectMessage.java:151: warning: non-varargs call of varargs method with inexact argument type for last parameter;
return (FederationPolicy) Class.forName(clazz).getConstructor(null).newInstance();
cast to Class<?> for a varargs call
cast to Class<?>[] for a non-varargs call and to suppress this warning
```
```
An error occurred while running github feature in .asf.yaml!:
.asf.yaml: Invalid GitHub label 'Apache' - must be lowercase alphanumerical and <= 35 characters!
```
Update netty version to 4.1.43.Final and netty-tcnative version to 2.0.26.Final.
Change restricted-security-client.policy because Netty 4.1.43.Final requires
access to two more files: /etc/os-release and /usr/lib/os-release.
> When making use of a feature in .asf.yaml, please ensure that you have discussed this with the entire project first, and have understood what the configuration changes will do to your workflow and project resources.
> ~~ https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories
I believe that the github config part (setting tagline and project labels) is mostly harmless.
The GitHub project page currently has a somewhat random set of tags at the top,
so this should be a big improvement.
https://github.com/apache/activemq-artemis currently contains the following tags
php, activemq, c, network-client, ruby, python, csharp, cplusplus, java, perl, network-server
This is to make it possible to identify what test is leaking files whenever that is happening.
That is because future tests will report the leaks, and it's difficult to identify where it happened.
Also i'm changing NoProcessFilesBehind to show the getOpenFD propertly
Some open wire tests will close a consumer and open it right away.
The removal of the queue is asynchronous, having this kind of behaviour may lead to issues
after we moved the QueueManager to be asynchronous.