Add feature flags endpoint support

[crodriguesbr]

Why this PR?

• Adds endpoint filter support for feature flags in .NET 7+ applications
• Enables declarative feature flag control at the endpoint level
• Simplifies feature management integration with minimal code

Visible Changes

• New WithFeatureGate extension method for endpoints
• Returns 404 when feature is disabled

Example usage:
endpoints.MapGet("/api/feature", () => "Feature Enabled") . WithFeatureGate("MyFeature");

• Requires .NET 7.0 or greater

[crodriguesbr]

@microsoft-github-policy-service agree

[zhiyuanliang-ms]

@crodriguesbr Thank you for contributing to the feature management repo! This PR is related to #253

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

[zhiyuanliang-ms]

Hi, @crodriguesbr

My team have reviewed this PR. We generally agree with the code implementation. This is a new cool feature. Thank you so much for sending out this PR. ❤️

Except for the comment I left, there are still some nits or code style issues about this PR.

We do have linting rules in the .editorconfig file but the rule set is used by all of our C# code base. So we only keep the “greates common divisor`. There are some code style conventions which is specific to this repo. We do want our code bases to be consistent and looks like written by one person.

Would you mind if I take over this PR to address the code style issues? If no, I can left comments for those issues.

[zhiyuanliang-ms]

BTW, could you also update the PR description as the example usage has changed. @crodriguesbr

[crodriguesbr]

BTW, could you also update the PR description as the example usage has changed. @crodriguesbr

Done!

[crodriguesbr]

Hi, @crodriguesbr

My team have reviewed this PR. We generally agree with the code implementation. This is a new cool feature. Thank you so much for sending out this PR. ❤️

Except for the comment I left, there are still some nits or code style issues about this PR.

We do have linting rules in the .editorconfig file but the rule set is used by all of our C# code base. So we only keep the “greates common divisor`. There are some code style conventions which is specific to this repo. We do want our code bases to be consistent and looks like written by one person.

Would you mind if I take over this PR to address the code style issues? If no, I can left comments for those issues.

Hi, @zhiyuanliang-ms

Thank you for your kind words about this PR! I'm happy your team finds this helpful feature.

Regarding the code style issues, I completely understand the importance of keeping the codebase consistent. I'd prefer to address these issues myself, as it would help me better understand your conventions for future contributions. If you could leave comments outlining the needed changes, I'd happily adjust them.

Looking forward to your feedback!

Best regards,
@crodriguesbr