Fixing DatabaseCluster proxysql resource requests

[Ankit152]

CHANGE DESCRIPTION

Problem:
Issue: #938

Short explanation of the problem.

When creating a DatabaseCluster with proxy.type: proxysql, the everest-operator panics with assignment to entry in nil map inside applyProxySQLCfg. The cluster gets stuck in creating status indefinitely and never provisions any pods.

Related pull requests

• [link]

Cause:
In defaultSpec(), the ProxySQL spec initializes Resources.Limits but never initializes Resources.Requests, leaving it as a nil map:

ProxySQL: &pxcv1.ProxySQLSpec{
    PodSpec: pxcv1.PodSpec{
        Resources: corev1.ResourceRequirements{
            Limits: corev1.ResourceList{...},  // initialized
            // Requests is nil, never initialized
        },
    },
},

Solution:
Short explanation of the solution we are providing with this PR.

CHECKLIST

Helm chart

• Is the helm chart updated with the new changes? (if applicable)

Jira

• Is the Jira ticket created and referenced properly?

Tests

• Is an Integration test/test case added for the new feature/change?
• Are unit tests added where appropriate?

[recharte]

Thank you @Ankit152, left a few suggestions.