Flaky test: modifying memoryLimit for container in Devfile

[rm3l]

/kind bug
/area testing

Examples:

• https://s3.eu-de.cloud-object-storage.appdomain.cloud/odo-tests-openshift-logs/pr-6586-openshift-tests-4060.txt

Timed out after 180.001s.
  Expected
      <string>:  ⚠  Pod is Terminating
       ✗  Finished executing the application (command: devrun) [40s]
       ⚠  No pod exists
       ⚠  Pod is Pending
       ✓  Pod is Running
       •  Syncing files into the container  ...
      
 ✓  Syncing files into the container [382ms]
       •  Building your application in container (command: devbuild)  ...
      
 ✓  Building your application in container (command: devbuild) [6s]
       •  Executing the application (command: devrun)  ...
       -  Forwarding from 127.0.0.1:42585 -> 3000
      
      ↪ Dev mode
       Keyboard Commands:
      [Ctrl+c] - Exit and delete resources from the cluster
           [p] - Manually apply local changes to the application on the cluster
      
  To satisfy at least one of these matchers: [%!s(*matchers.ContainSubstringMatcher=&{Pushing files... []}) %!s(*matchers.ContainSubstringMatcher=&{Updating Component... []})]
  In [BeforeEach] at: /go/odo_1/tests/helper/helper_run.go:64
------------------------------
Summarizing 1 Failure:
  [FAIL] odo dev command tests port-forwarding for the component when devfile has single endpoint when running odo dev when modifying memoryLimit for container in Devfile [BeforeEach] should react on the Devfile modification
  /go/odo_1/tests/helper/helper_run.go:64

Ran 421 of 771 Specs in 1277.997 seconds
FAIL! -- 420 Passed | 1 Failed | 0 Pending | 350 Skipped

Originally posted by @rm3l in #6586 (comment)

[anandrkskd]

More failure on IBM-Cloud CI - https://s3.eu-de.cloud-object-storage.appdomain.cloud/odo-tests-openshift-logs/pr-6484-openshift-tests-4177.txt