fix(ingestProposal): fix/handle no-op ingestion

[david-leifker]

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[RyanHolstien]

Approving, but should the runId index occur if the optional is empty? What does a no-op mean and when does this scenario occur?

[david-leifker]

The case where this might happen is when the ingestion proposal is a key aspect that already exists in the database. In that case there is no write and thus no result object to return. If there is no result, then we default to false to avoid updating the runId on the ES document because no actual write occurred due to the MCP.

[david-leifker]

In most cases, the result not used or is discarded.