(neptune-alpha): Verification of matching engineVersion and parameterGroup version

### Describe the feature

Verifies whether the parameterGroupFamily set corresponds to the specified engineVersion.

### Use Case

In Neptune, there are engine versions such as 1.0 series, 1.2 series, and 1.3 series, and it's necessary to set the corresponding version of the parameterGroupFamily for these engines.
For instance, if you set a v1.0 parameterGroupFamily for a cluster with an engineVersion in the v1.2 series, an error will occur during deployment.

```sh
aws-cdk-neptune-integ | 24/33 | 1:49:54 AM | CREATE_FAILED | AWS::Neptune::DBCluster | Database (DatabaseB269D8BB) Resource handler returned message: "The Parameter Group paramsa8366201-js9btllrt8cs with DBParameterGroupFamily neptune1 cannot be used for this instance. Please use a Parameter Group with DBParameterGroupFamily neptune1.2 (Service: Neptune, Status Code: 400, Request ID: 2c609029-86e7-432c-aac7-5b39623c054c)" (RequestToken: 293c5e39-f5d4-16cf-8e8d-770ce94aab37, HandlerErrorCode: InvalidRequest)
```

I would like to make these errors detectable at the time of running cdk synth.

### Proposed Solution

_No response_

### Other Information

https://docs.aws.amazon.com/neptune/latest/userguide/parameter-groups.html

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.116.1

### Environment details (OS name and version, etc.)

irrelevant

Start at the Neptune construct's cdk synth path and inspect how engineVersion and parameterGroupFamily are represented; the issue does not name a source file or test. Use the linked Neptune parameter-group documentation and the 1.0, 1.2, and 1.3 examples as compatibility cases, with the work complete when an invalid pairing is reported during cdk synth rather than deployment.

Written by the indexing model from the issue text.