set memory limits for eosxd

Following on from an issue with a user's cluster where eosxd-csi appeared to be consuming large amounts adding somewhat generous limits to prevent a big memory leak from consuming a node.

These are drawn somewhat heuristically from looking at the large clusters than consume eosxd-csi (gitlab,swan, ...).

added A-runtime A-storage p3 labels

requested review from @strigazi

assigned to @jmunday

changed milestone to %R-2025-Q1-1

Will you push something similar to the eos chart?

resolved all threads

approved this merge request

mentioned in commit 8dcb4be9

merged