Description of problem:

When running an application analysis or previous tasks (tech-discovery) the execution of some rules times out due to insufficient storage, however, the surfaced error is "unable to ask for Konveyor rule entry"

Version-Release number of selected component (if applicable): 7.3

How reproducible: Always 

Steps to Reproduce:
1. Deploy MTA with the following Tackle CR Configuration

kind: Tackle
apiVersion: tackle.konveyor.io/v1alpha1
metadata:
  name: tackle
  namespace: openshift-mta
spec:
  feature_auth_required: 'true'
  provider_java_container_limits_memory: "2Gi"
  provider_java_container_requests_memory: "2Gi"
  hub_bucket_volume_size: "5Gi"
  hub_database_volume_size: "2Gi"
  maven_data_volume_size: "5Gi"
  # Size requested for the cache volume; ignored when rwx_supported=false
  cache_data_volume_size: "1Gi"
  pathfinder_database_data_volume_size: "2Gi"
  rwx_supported: "false" 

2. Create an application (tackle-testapp) and start an analysis on it 

Actual results:

The tech discovery tasks takes more than 10 minutes and the analysis fails with multiple "unable to ask for Konveyor rule entry"

Expected results:

1. The execution of the rules should take longer before timing out.
2. If the analysis fails due to OOM the error should be surfaced to the user.

Additional info:
Attached you'll find the logs from one of the users that reproduced this.
Note: This is only reproducible with containers, CLI is not affected by this bug.