Port MYFACES-4117 (No default name for @FacesComponent with createTag=true and no tagName)

[volosied]

Describe the bug
No default tag name is provided when creating a custom component with @FacesComponent with createTag=true.

/index.xhtml at line 11 and column 28 <t:someComponent> Tag Library supports namespace: http://xmlns.jcp.org/jsf/component, but no tag was defined for name: someComponent

Stack trace will look similar to:

javax.faces.view.facelets.TagException: /index2.xhtml at line 11 and column 28 <t:dummyComponent> Tag Library supports namespace: http://xmlns.jcp.org/jsf/component, but no tag was defined for name: dummyComponent
	at org.apache.myfaces.view.facelets.compiler.CompilationManager.pushTag(CompilationManager.java:300)
	at org.apache.myfaces.view.facelets.compiler.SAXCompiler$CompilationHandler.startElement(SAXCompiler.java:251)
	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
	at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:183)

Steps to Reproduce
As mentioned, create a component using @FacesComponent with createTag=true.

For example:

@FacesComponent(value = SomeComponent.COMPONENT_TYPE, createTag = true)
public class SomeComponent extends UIComponentBase {

Expected behavior
No exceptions should occur. Developer should be able to use a tag with the default name. The default name will be the component's class, but the first letter lowercase. SomeComponent use use the tag name: someComponent.

Diagnostic information:

• OpenLiberty Version: All Versions
• Affected feature(s) jsf-2.2
• Java Version: N/A

Additional context
https://issues.apache.org/jira/browse/MYFACES-4117
Workaround is use specify a tag name: https://docs.oracle.com/javaee/7/api/javax/faces/component/FacesComponent.html#tagName--