feat(flags): Capture flagpole and option automator results using new SDK interfaces

[cmanallen]

Upgrades the SDK and removes the old integration code.

.

[codecov]

Codecov Report

Attention: Patch coverage is 94.11765% with 1 line in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/sentry/features/manager.py	83.33%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #84724      +/-   ##
==========================================
- Coverage   87.88%   87.71%   -0.17%     
==========================================
  Files        9564     9646      +82     
  Lines      541696   545027    +3331     
  Branches    20863    21391     +528     
==========================================
+ Hits       476044   478063    +2019     
- Misses      65312    66627    +1315     
+ Partials      340      337       -3     

[aliu39]

Maybe we should add feature.- prefixes like we do for FE? And option.- for options

[cmanallen]

@michellewzhang If I emit options which are integers or floats or strings how will the front-end respond?

[michellewzhang]

@michellewzhang If I emit options which are integers or floats or strings how will the front-end respond?

what do you mean by options?

[michellewzhang]

if you're referring to flag evaluation results, the frontend is typed to require a boolean result so i'd have to update that type to avoid breaking things.

[michellewzhang]

flag types are defined here:

sentry/static/app/types/event.tsx

Line 649 in 09c1f7e

export type FeatureFlag = {flag?: string; result?: boolean};

[getsentry-bot]

PR reverted: 05b095b