feat: add featureFlags param

[ascandone]

this is noop PR, but it involves changing the publicly exposed function, which we'll want to design in a way that will be backwards compatible in the future

[codecov]

Codecov Report

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

Project coverage is 63.24%. Comparing base (fd2a1e0) to head (778896f).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/cmd/run.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   63.21%   63.24%   +0.02%     
==========================================
  Files          28       28              
  Lines        6206     6211       +5     
==========================================
+ Hits         3923     3928       +5     
  Misses       2115     2115              
  Partials      168      168              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ascandone]

Here we add a new publicly exposed function which has a featureFlags map[string]struct{} param
We have a map with untyped keys instead of a struct so that removing feature flags is not a breaking change

[ascandone]

we pass the feature flags here directly (without further design patterns e.g. dependency injection). When a fflag will be available, we will parse it as a boolean field in the programState struct

this way

1. we can still control presence/absence of fflags in tests
2. the runtime will have access to passed feature flags in each moment