Story details: https://app.shortcut.com/launchdarkly/story/205159

This pull request was auto generated by the Launchdarkly Github
Standards automation platform.

* Add default SECURITY.md file

This pull request was auto generated by the Launchdarkly Github
Standards automation platform.

* Add default CODEOWNERS file

This pull request was auto generated by the Launchdarkly Github
Standards automation platform.

* Add default SECURITY.md file

This converts the repo to Github Actions for CI.

Of note, the Github windows runner does not support containers, so it's
using a Chocolatey package for Redis.

Additionally, to get the redis cluster networking to work properly when
using the `services` config, I had to run the CI job in a container
rather than on the `ubuntu-latest` runner itself. So, it's running in
`ubuntu:22.04` with essential packages installed.

In my original PR that introduced Github Actions, the tests on windows
were not actually succeeding. This issue was masked by `go test` caching
previous (successful) results.

This PR fixes the tests by running `redis-server` in the background, and
additionally adds a `count=1` argument to `go tests` to ensure this type
of issue does not happen again.

When using `==`, this comparison will fail if the error is wrapped (for
example, to add some common prefix string to the error message.)

The solution is to use `errors.Is`, which will check down the chain.

Release-As: 1.0.0

🤖 I have created a release *beep* *boop*
---


##
[1.0.0](v1.0.0-beta.1...v1.0.0)
(2024-09-12)


### Miscellaneous Chores

* release 1.0.0
([#24](#24))
([2897feb](2897feb))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>