feat(Data/neo4jDatabases): add Neo4j resource type and Kubernetes recipe

[superbeeny]

Description

Replacement PR #45

Related GitHub Issue:

Testing

Contributor Checklist

• File names follow naming conventions and folder structure
• Platform engineer documentation is in README.md
• Developer documentation is the top-level description property
• Example of defining the Resource Type is in the developer documentation
• Example of using the Resource Type with a Container is in the developer documentation
• Verified the output of rad resource-type show is correct
• All properties in the Resource Type definition have clear descriptions
• Enum properties have values defined in enum: []
• Required properties are listed in required: [] for every object property (not just the top-level properties)
• Properties about the deployed resource, such as connection strings, are defined as read-only properties and are marked as readOnly: true
• Recipes include a results output variable with all read-only properties set
• Environment-specific parameters, such as a vnet ID, are exposed for platform engineers to set in the Environment
• Recipes use the Recipe context object when possible
• Recipes are provided for at least one platform
• Recipes handle secrets securely
• Recipes are idempotent
• Resource types and recipes were tested

[superbeeny]

@Reshrahim new PR

[Reshrahim]

Thanks for the contribution @superbeeny. I tested the Recipe deployment and it seems to be working

Suggested minor changes for consistency across definitions in the repo.

[Reshrahim]

For consistency across definitions, would be good to follow this format for Recipe input and output properties -https://github.com/radius-project/resource-types-contrib/blob/main/Data/mySqlDatabases/README.md

[zachcasper]

The resource type definition looks good to me. I did not test the recipe. It's difficult to test without a test application.