[proposal] Refine the runtime calculation mechanism when parent ElasticQuota submit Pods.

[xulinfei1996]

What is your proposal:
Refine the runtime calculation mechanism when parent ElasticQuota submit Pods.

Why is this needed:
If we allow the parent ElasticQuota submit Pods, there are several issues we should notice.
First, when parent ElasticQuota submit Pods, the Min of the child ElasticQuota may not satisfy.
Second, the calculation process of the runtime needs to deduct the usage of the parent node

Is there a suggested solution, if so, please add it:

[stale]

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close
  Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Reopen this PR with /reopen
  Thank you for your contributions.