When there are preset values in the matching rule, the field is still marked as required

[Finenyaco]

Describe the bug

Steps to reproduce

1. New a resource definition.
2. Add two matching rule using template bulitin/aws-rds-mysql.
3. Fill in different “Vpc Id” in the two rules and save.
4. Check the resource definition UI Schema.

Result

1. 'VPC ID' is marked as required.

Expected behavior

When there are preset values in the matching rule, it should remove the field from the required list in the schema automatically.

Environment

• Walrus version: v0.5.0

Additional context
Add any other context about the problem here.

[Finenyaco]

Environment

• Walrus version: main 57e7bb8
• UI version: dev-a712ac5

Test Result:

1. Create a resource definition using a template that includes a required list-type variable.
2. Add two matching rules with different values.
3. Check the definition UI schema. The variable is still required.

Another enhancement: #2097

[Finenyaco]

Environment

• Walrus version: main 5d939cc
• UI version: dev-a712ac5

Test Result:

This issue still can be reproduced in variables of type list(map(string)).

[Finenyaco]

Environment

• Walrus version: main bd8b2f4
• UI version: v0.5.1-rc1

Test Result:

Multiple required properties under a required object-type attribute, some of which have values set in the matching rules, while others do not, result in all properties becoming optional in the merged schema.

• Check the matching rule:

• Check the definition UI schema:

[Finenyaco]

Environment

• Walrus version: main ddec5a8
• UI version: dev-be9a1a4

Test Result:

It can be reproduced using the following variable definitions:

• template:

• resource definition UI schema:

[Finenyaco]

Environment

• Walrus version: main b926a09
• UI version: dev-5eecc2b

Test Result: pass

• One required property.

• No required property.