[system testing] Apply cpu and memory limits to match Agentless

In an effort to catch resource constraint related issues, it would be useful to apply container cpu and memory limits to the agent container that elastic-package starts for system testing. Ideally those limits would match what is defined in the package's manifest.yml (or if unspecified, use the defaults that are applied to agentless containers).