[new rule]: Linting Rule for top level resource that supports Private Endpoints

### Lint rule description

When a resource supports private endpoints, the property bag of the resource should contain:
1. A `privateEndpointConnections` property
2. A `publicNetworkAccess` property

### 1. For `privateEndpointConnections` in Property Bag

Essentially the property bag will contain a “privateEndpointConnections” property which is an array of
“PrivateEndpointConnections” whose schema matches exactly with the PrivateEndpointConnection schema in [privatelinks.json](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v3/privatelinks.json#L20) from the common types, minus the top level properties (except `id`)

### 2. For `publicNetworkAccess` flag
Essentially, the parent resource’s property bag will contain a “publicNetworkAccess” field which would be of an enum type with atleast _Enabled_ and _Disabled_ values.

```json
{
"properties": {
...,
"publicNetworkAccess": "Enabled" | "Disabled",
...
}
}
```
### When to trigger the rule?

The rule can be triggered by inferring the parent resource that supports private endpoints (similar to [Rule 4035](https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/openapi-authoring-automated-guidelines.md#r4035-privateendpointresourceschemavalidation)). We can infer the parent resource from ‘../{parentResource}/privateEndpointConnections` path and check all ‘../{parentResource}’ definitions.

### Related swagger example

The swagger for the `privateEndpointConnections` property matches the one contained in [privatelinks.json](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/common-types/resource-management/v3/privatelinks.json#L20) in the common types. It can be moved to a common type so that it can be used for both the parent resource as well as the schema for `PrivateEndpointConnections` resource type

### Category

ARM

### Severity level

Error

### Applies to

RPaaS API spec

### How to fix the violation

Adding the required properties in the property bag should fix the violation

### What't the impact if breaking the rule

Certain properties are expected by RPaaS and in the parent resource property bag. If the rule is violated, Swagger validation would fail for these properties and cause issues in Private Enpoint related scenarios