[RS-DEF] Enhance Eventstream resource by adding definition support

[DariuszPorowski]

📝 Description

When I am managing my Infrastructure as Code using Terraform for Eventstream. I want to be able to manage definition. So, I can automate the deployment and configuration of my Eventstream definition, ensuring consistency, and reducing manual effort.

🔬 Details / References

• Resource Name: fabric_eventstream
• API documentation:
  • https://learn.microsoft.com/en-us/rest/api/fabric/eventstream/items/get-eventstream-definition
  • https://learn.microsoft.com/en-us/rest/api/fabric/articles/item-management/definitions/eventstream-definition
• Estimated complexity/effort: easy
• Related resources/data-sources: https://registry.terraform.io/providers/microsoft/fabric/latest/docs/resources/eventstream

🚧 Potential Terraform Configuration / Desired Solution

# Example 1 - Eventstream without definition
resource "fabric_eventstream" "example" {
  display_name = "example"
  workspace_id = "00000000-0000-0000-0000-000000000000"
}

# Example 2 - Eventstream with definition bootstrapping only
resource "fabric_eventstream" "example_definition_bootstrap" {
  display_name              = "example"
  description               = "example with definition bootstrapping"
  workspace_id              = "00000000-0000-0000-0000-000000000000"
  definition_update_enabled = false
  definition = {
    "eventstream.json" = {
      source = "${local.path}/eventstream.json.tmpl"
    }
  }
}

# Example 3 - Eventstream with definition update when source or tokens changed
resource "fabric_eventstream" "example_definition_update" {
  display_name = "example"
  description  = "example with definition update when source or tokens changed"
  workspace_id = "00000000-0000-0000-0000-000000000000"
  definition = {
    "eventstream.json" = {
      source = "${local.path}/eventstream.json.tmpl"
      tokens = {
        "MESSAGE" = "World"
        "MyValue" = "Lorem Ipsum"
      }
    }
  }
}

📎 Additional context

• Definition is optional
• Format is N/A

✅ Definition of Done

• Data Transfer Objects (DTOs)
• Data Client functions
• Resource Implementation
• Resource Added to Provider
• Unit Tests for Happy path
• Unit Tests for Error path
• Acceptance Tests
• Example in the ./examples folder
• Schema documentation in code
• Updated auto-generated provider docs with task docs

🔰 Code of Conduct

• I agree to follow this project's Code of Conduct.