feat!: remote "contrib" from namespaces and package names

[askpt]

Signed-off-by: André Silva 2493377+askpt@users.noreply.github.com

This PR

This pull request performs a comprehensive renaming and migration of the Flagd provider package from the OpenFeature.Contrib.Providers.Flagd namespace and directory structure to OpenFeature.Providers.Flagd. This change affects all source files, tests, documentation, configuration, and build/release files, aligning the Flagd provider with the new naming convention and repository structure.

Key changes include:

Namespace and Directory Renaming:

• All source files, test projects, and related submodules for the Flagd provider have been moved from the OpenFeature.Contrib.Providers.Flagd path and namespace to OpenFeature.Providers.Flagd. All internal references, namespaces, and using statements have been updated accordingly. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

• The FlagdSchema.cs file has been removed as part of this migration.

Project and Build Configuration:

• The main project file has been renamed to OpenFeature.Providers.Flagd.csproj and updated to use the new package ID. All solution (.slnx), component ownership, and submodule configuration files have been updated to reference the new paths. [1] [2] [3] [4] [5] [6]

• The release configuration and manifest files have been updated to reflect the new package name and path for the Flagd provider. [1] [2]

Documentation and Contribution Guidelines:

• All documentation, including the README and CONTRIBUTING guides, has been updated to use the new package name and namespace. This includes code samples, package installation instructions, and references to test projects. [1] [2] [3] [4] [5] [6]

These changes ensure consistency in naming across the codebase and documentation, and prepare the Flagd provider for future releases under the new structure.

Related Issues

Fixes #425

[gemini-code-assist]

Code Review

This pull request renames the Flagd provider from OpenFeature.Contrib.Providers.Flagd to OpenFeature.Providers.Flagd across the entire repository, updating namespaces, project paths, documentation, and configuration files. Feedback was provided regarding the redundant and technically incorrect use of the DestinationFolder attribute in the new E2E test project files, as it is not a standard MSBuild property for None items and conflicts with the CopyToOutputDirectory setting.

[toddbaert]

@askpt fine with me! Thanks for making this consistent.

IIRC, in Nuget, you can deprecate packages and actually specify new ones. Will you do this after this merge?

[askpt]

@askpt fine with me! Thanks for making this consistent.

IIRC, in Nuget, you can deprecate packages and actually specify new ones. Will you do this after this merge?

No. I will do after the package release. We need to release OpenFeature.Providers.Flagd first. I will do exactly what we did for GoFF.