Remove rulesets_etags output to eliminate permadrift

[Copilot]

The GitHub API non-deterministically returns strong vs. weak ETags ("abc..." vs W/"xyz...") for the same ruleset resource, causing rulesets_etags to show spurious changes on every plan/apply cycle.

Changes

• outputs.tf — removed rulesets_etags output; ETags are HTTP caching internals with no stable semantic value for module consumers
• examples/complete/outputs.tf, examples/minimum/outputs.tf — removed corresponding passthrough outputs
• test/src/examples_complete_test.go — removed etag output fetch and length assertion

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Permadrift from etags</issue_title>
<issue_description>### Describe the Bug

I am noting permadrift with rulesets. For example:

Changes to Outputs:
  ~ rulesets_etags               = {
      ~ main_branch_protection = "\"7e66b1d2703c08ce8ad4fd6c33f02f1fadc029278e88b0a5a189346c6b0386ee\"" -> "W/\"02ffd1a67e695b87303db4ab4fb71ad52d60a76e7c021cca8db01a365e21927a\""
    }

Expected Behavior

No drift on outputs on subsequent plan/applies

Steps to Reproduce

Happens on subsequent plan/applies

Screenshots

No response

Environment

No response

Additional Context

No response</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Permadrift from etags #18

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.