Add FilOzzy bot

[BigLep]

In support of #10

Reviewer's Checklist

• It is clear where the request is coming from (if unsure, ask)
• All the automated checks passed
• The YAML changes reflect the summary of the request
• The Terraform plan posted as a comment reflects the summary of the request

[BigLep]

I'm going to self review/approve because the risk here is low and I want to get more setup for #10

[github-actions]

The following access changes will be introduced as a result of applying the plan:

Access Changes

User filozzy:
  - will join the organization as a [object Object] (remind them to accept the email invitation)

[github-actions]

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

FilOzone

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # github_membership.this["filozzy"] will be created
  + resource "github_membership" "this" {
      + downgrade_on_destroy = false
      + etag                 = (known after apply)
      + id                   = (known after apply)
      + role                 = "member"
      + username             = "FilOzzy"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

[Copilot]

Pull Request Overview

This PR adds the FilOzone bot to the GitHub organization’s membership roster.

• Updated members list to include the new bot account.
• Ensured the YAML file reflects the request from issue #10.

Comments suppressed due to low confidence (1)

github/FilOzone.yml:16

• The PR title refers to 'FilOzzy' but the username added is 'FilOzone'. Please confirm the correct bot username and ensure consistency.

    - FilOzone