feat!: Bootstrap project and implement env-var provider

[bencehornak]

This PR

Depends on open-feature/kotlin-sdk#148

• Creates the basic Gradle structure with the usual plugins (tried to follow the kotlin-sdk here)
• Adds the usual Markdown files (similar to java-sdk-contrib)
• Initializes GitHub Actions, renovate, release-please
• Adds the env-var provider

Notes

There is ongoing work to make the Kotlin SDK multiplatform-based, see open-feature/kotlin-sdk#148. I suggest this and the other PR to be reviewed together and to build this repo against locally published artifacts of the Kotlin SDK based on the other PR.

Feel free to push to the branch, lmk if you need access to it.

To do

• Set up GitHub Actions (might need tweaking due to the new KMP platforms)
• Set up Renovate -> HELP NEEDED
• Set up Release-Please -> will be done in Configure Release-please #2
• Set up publishing -> HELP NEEDED
• Set up FOSS score? -> would do later to keep this PR small
• Decide and document supported KMP platforms of the env-provider
• Double check OWNERS -> I just took the list from the community project, but we need the consent of the maintainers to assume the maintainer role of this repo -> HELP NEEDED
• Review GitHub repo settings

... let me know, if further points are missing, I can add them to the list.

How to test

As far as the env-var provider is concerned I'm planning to create a KMP example app as part of open-feature/kotlin-sdk#148, we can make use of that to test it.

There are many other things to test, mainly the CI and the publishing, we will surely notice problems with those.

[beeme1mr]

I've only made it part way through the review but I wanted to leave some initial thoughts.

[beeme1mr]

Thanks for getting this started, @bencehornak! Let's see what @toddbaert says about the Release Please config.

[beeme1mr]

Hey @bencehornak, could you please remove the Release Please config from this PR and open a separate issue? It will take a bit to get that setup and I don't want to hold up this PR.

[bencehornak]

@beeme1mr done, I have moved the Release-please files to #2, please feel free to take it over from me.

[bencehornak]

The ci.yaml GH Actions pipeline hasn't run, I'm not sure why... it's not waiting for maintainer approval as far as I can tell.

[beeme1mr]

The ci.yaml GH Actions pipeline hasn't run, I'm not sure why... it's not waiting for maintainer approval as far as I can tell.

I believe this is a security mechanism in GitHub to prevent people from leaking secrets. It should run for future PRs once this has been merged.

I'm going to get this in now. Thanks @bencehornak for your hard work.