Add logs in case data-ingest token is not provided

[gkrenn]

Description

The data-ingest token is propagated to the endpoint-properties file even if the field is empty. To make it easier to debug the issue and tell the user what it could be this PR:

• Creates and additional log line when the secret is created to inform the user that the token is missing
• Adds a message to the token condition in the DynaKube to tell if the token was not provided

Jira

How can this be tested?

• Create a DynaKube with metadata enrichment enabled & data-ingest token missing
• Check for log line "data ingest token not found in secret" and the token conditions on the DynaKube

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.58%. Comparing base (1794e47) to head (88f988f).
Report is 1 commits behind head on main.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4089      +/-   ##
==========================================
+ Coverage   64.57%   64.58%   +0.01%     
==========================================
  Files         400      400              
  Lines       26773    26784      +11     
==========================================
+ Hits        17288    17299      +11     
  Misses       8128     8128              
  Partials     1357     1357              

Flag	Coverage Δ
unittests	64.58% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[wepudt]

lgtm