Spike: Upsert and Delete should preempt updates with no changes

[ja20222]

Do not generate the configuration if there have be no operative changes in the k8s resources

Acceptance criteria:

• evaluate options for achieving this
• capture them in a doc
• make a decision
• define work

[mpstefan]

Not enough information to prioritize.

@pleshakov Can you add context?

Who cares about this?
What configuration?
Why do we want this? What impact does it have?

[pleshakov]

This is related to #1664 but different.

An example of the problem that this issue considers:
If some resource like HTTPRoute changes (ex - a new parentRef was added for a non-NGF Gateway), but the generated configuration is the same as the current one, we should skip reloading NGINX.