CodeAction for cvc-complex-type.2.4.b: "insert all expected" vs. "insert all possible"

[GitMensch]

the code action says "Insert all expected elements" - but it also inserts elements with "minOccurs="0" maxOccurs="1" --> so also optional elements (and then complains that those have an invalid data type, manually deleting those lead to a warning free xml) -> can you split this into two actions "insert all expected" and "insert all possible"?

Originally posted by @GitMensch in #1218 (comment)

[angelozerr]

Could you give us a very simple ml and xsd for this issue. We could use them for tests.

Thanks!

[GitMensch]

Not complete but possibly enough:

	<xs:element name="cmplx">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="a" minOccurs="1" maxOccurs="1"/>
				<xs:element name="b" minOccurs="0" maxOccurs="1"/>
				<xs:element name="c" minOccurs="0" maxOccurs="1"/>
				<xs:element name="d" minOccurs="1" maxOccurs="1"/>
				<xs:element name="e" minOccurs="1" maxOccurs="1"/>
			</xs:sequence>
		</xs:complexType>
	</xs:element>

and

	<cmplx>
	</cmplx>

[JessicaJHee]

I'm interested in this issue!