fix: ResourceGroup unnecessary condition updates

[karlkfi]

The ResourceGroup controller has been updating the Reconciling
status condition to status=True and back to status=False every time
it attempts to reconcile. This is unnecessary and expensive. There
are no side-effects during reconciling, and no clients need to know
when the ResourceGroup controller is reconciling. In fact, this
causes several problems:

• kstatus constantly flaps from Current to InProgress
• the resourceVersion is constantly going up
• etcd is being filled up with changes, increasing memory and storage
• watch events are being propegated to controllers, like the RGC,
  which triggers perpetual unnecessary updates.

This change fixes that problem by removing the initial status update
that set Reconciling status=True and also removing the case where
status=False with reason=ExceedTimeout. This means the Reconciling
condition will always be set to status=False after the ResourceGroup
controller has reconciled.

This deprecates the Reconciling condition, without fully removing
it, in case some client was still waiting for its status=False.

This should reduce the number of ResourceGroup status updates, and
reduce confusion by users who assumed that the Reconciling condition
was an aggregate of status.resourceStatuses.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from karlkfi. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment