Microsoft.DataFactory/factories/triggers: Status is Stopped

### Resource Type

Microsoft.DataFactory/factories/triggers

### Api Version

2018-06-01

### Issue Type

Missing property(s)

### Other Notes

According to the [documentation](https://learn.microsoft.com/en-us/azure/templates/microsoft.datafactory/factories/triggers?pivots=deployment-language-bicep#blobeventstrigger) of the `BlobEventsTrigger` you can define "pipelines that need to be started".

However by specifying the trigger it shows up as 'Stopped' in the trigger overview in the Azure Data Factory Studio.

If I export the ARM template I see the following in the config:
```
resource factoryName_OnNewBlob 'Microsoft.DataFactory/factories/triggers@2018-06-01' = {
name: '${factoryName}/OnNewBlob'
properties: {
description: 'Triggers when a new blob is created'
annotations: []
runtimeState: 'Started'
pipelines: [
...
```

However `runtimeState` is a read-only property. In the Studio the following property is available but it doesn't seem that there is a option to specify it in a bicep template.

### Bicep Repro

This is my bicep template:
```
resource OnNewBlobTrigger 'Microsoft.DataFactory/factories/triggers@2018-06-01' = {
name: 'OnNewBlob'
parent: DataFactory
properties: {
description: 'Triggers when a new blob is created'
pipelines: [
{
pipelineReference: {
referenceName: DataFactoryPipeline.name
type: 'PipelineReference'
}
parameters: {
sourceFolder: '@triggerBody().folderPath'
sourceFile: '@triggerBody().fileName'
}
}
]
type: 'BlobEventsTrigger'
typeProperties: {
blobPathBeginsWith: '/containername/blobs/'
ignoreEmptyBlobs: true
scope: blobScope
events: [
'Microsoft.Storage.BlobCreated'
]
}
}
}
```

### Confirm

- [X] I have read the troubleshooting guide and looked for duplicates.

Start with the Microsoft.DataFactory/factories/triggers resource at API version 2018-06-01 and compare its Bicep schema with the BlobEventsTrigger documentation and exported ARM template. Determine whether the Azure service exposes a deployable property for the Studio trigger state; done means the supported property is represented in the type definition and the reported deployment behavior is addressed.

Written by the indexing model from the issue text.