feat(default-memory-limits): set default memory limits

[ryanhristovski]

Reverts #4979 and removes the shutdown manager configuration for now.

The issue for failed CI was shutdown-manager oomkilling. While I do some benchmarking on this service to determine what a good memory limit will be using this comment as a starting point #4960 (comment). I am going to go ahead and continue with the default memory limits.

Original PR: #4960

[ryanhristovski]

Not sure why DCO is failing here, but PR is ready

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.86%. Comparing base (c499b41) to head (cc2d2b8).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5032      +/-   ##
==========================================
+ Coverage   66.84%   66.86%   +0.01%     
==========================================
  Files         211      210       -1     
  Lines       32920    32950      +30     
==========================================
+ Hits        22007    22031      +24     
- Misses       9586     9587       +1     
- Partials     1327     1332       +5     

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

[zirain]

Not sure why DCO is failing here, but PR is ready

9b1f471 didn't signed.

[ryanhristovski]

is it possible the end to end tests are flaky?

on the last build it failed on e2e-test (v1.30.6, ipv4) and passed e2e-test (v1.31.4, ipv6)... now it's failing on e2e-test (v1.31.4, ipv6) with seemingly unrelated errors

[zirain]

/retest

[ryanhristovski]

@zirain need anything else to get this merged?

[zirain]

@ryanhristovski LGTM, please fix DCO.

[ryanhristovski]

/retest

[arkodg]

@ryanhristovski isnt this something that can be set using EnvoyProxy ?
if we are setting the requests and limits value to be equal, then we should reevaluate if 512M is the right default choice for most cases

[ryanhristovski]

@arkodg yes it can be set in EnvoyProxy but not having memory limits set by default can cause cluster-wide issues that I don't think we'd want to happen unintentionally.