An empty beans.xml is enough to activate CDI if it doesn't require an…

[psoares]

…y configuration.

The current file was creating an issue on Wildfly 12 and other servers. See https://access.redhat.com/solutions/4240421.

Motivation

Add references to relevant tickets or a short description about what motivated you do it. (E.g JIRA: https://issues.jboss.org/browse/AEROGEAR-{} AND/OR ISSUE: https://github.com/aerogear/standards/issues/{})
My project that uses this extension started not working at all for the last few days, without any code changes. Seems related to a new redirection on the beans xsd files. See https://access.redhat.com/solutions/4240421.

What

Add an short answer for: What was done in this PR? (E.g Don't allow users has access to the feature X.)
Removed the contents of beans.xml, since https://access.redhat.com/solutions/4240421 mentions if no configuration is done there, CDI is still activated by an empty beans.xml file.

Why

Add an short answer for: Why it was done? (E.g The feature X was deprecated.)
Because of Oracle's new redirects.

How

Add an short answer for: How it was done? (E.g By removing this feature from ... OR By removing just the button but not its implementation ... )

Verification Steps

After deploying a modified artifact to my local maven repo, my project works again.

Checklist:

• Code has been tested locally by PR requester
• Changes have been successfully verified by another team member

Progress

• Finished task
• TODO

Additional Notes

PS.: Add images and/or .gifs to illustrate what was changed if this pull request modifies the appearance/output of something presented to the users.