refactor(ui): stop using /meta/config endpoint

[erka]

/meta/config exposes too much configuration and UI doesn't need that much. There were few leakage of the secrets as people provide configuration options in their way and that fire seem never to stop.
The global idea is to drop /meta/config endpoint and this is a first step to it.

[codecov]

Codecov Report

Attention: Patch coverage is 86.95652% with 6 lines in your changes missing coverage. Please review.

Project coverage is 64.56%. Comparing base (ae0caa8) to head (929704f).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/flipt/main.go	0.00%	6 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3684      +/-   ##
==========================================
+ Coverage   64.41%   64.56%   +0.15%     
==========================================
  Files         170      170              
  Lines       17098    17132      +34     
==========================================
+ Hits        11013    11061      +48     
+ Misses       5400     5382      -18     
- Partials      685      689       +4     

Flag	Coverage Δ
unittests	64.56% <86.95%> (+0.15%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[erka]

@markphelps I have to add few tests but I looking for feedback on this.

[markphelps]

we have an opportunity to refactor this info API endpoint now I think?

maybe we should make the response it a bit more structured, something like:

{
  version: {
    current:
    latest: {
      version:
      URL:
    },
   build: {
    date: ,
    commit:
    goVersion:
    release:
   },
   authentication: {
    required: 
   },
   analytics: {
     enabled:
   },
   storage: {
    ...
  },
}

this would be an API response breaking change, but since the API is not documented for this endpoint maybe its ok?

wdyt?

[erka]

@markphelps I’ve updated the new fields to match the desired format. However, I'm not ready to update old fields in this PR, as it would introduce too many changes at once.

[markphelps]

That sounds good to me

[markphelps]

this looks great! thank you @erka