workflow update to mail error log w/signoff

[Jougan-0]

Notes for Reviewers

Update the workflow to send error logs whenever an error occurs while running mesheryctl registry generate. Additionally, create a new file to store only the errors.

Local run of the workflow.

Signed commits

• Yes, I signed my commits.

[github-actions]

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 27 lines in your changes missing coverage. Please review.

Project coverage is 9.19%. Comparing base (095d525) to head (fdda196).
Report is 69 commits behind head on master.

Files	Patch %	Lines
mesheryctl/internal/cli/root/registry/generate.go	0.00%	21 Missing ⚠️
mesheryctl/pkg/utils/formatter.go	0.00%	3 Missing ⚠️
mesheryctl/internal/cli/root/root.go	0.00%	2 Missing ⚠️
mesheryctl/pkg/utils/testing.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11156      +/-   ##
==========================================
- Coverage    9.20%    9.19%   -0.01%     
==========================================
  Files         145      145              
  Lines       19082    19091       +9     
==========================================
  Hits         1756     1756              
- Misses      17024    17033       +9     
  Partials      302      302              

Flag	Coverage Δ
unittests	9.19% <0.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.

[MUzairS15]

No need.
Use log instance, refer the existing approach which logs its output to registry log file.
Create a new log instance for errors logs when an error occurs use that log instance. As you initialize that instance set its log output to registry-generate-error.

Also make the directory structured, if you would.
logs/registry/1. log (contains logs of al severity except error logs) 2. error (contains only error logs)`

[Jougan-0]

Will do so positively.

[leecalcote]

Does this new email replace the existing email for this workflow or will it be a duplicate?

[Jougan-0]

Does this new email replace the existing email for this workflow or will it be a duplicate?

This will replace the component generator failure email in these scenarios:

• If the component generator job fails, the old failure email will be used.
  

• If the component generator is successful but the error log is not empty, a new email regarding the error logs will be sent, and the workflow will be marked as successful.
  

For the scenario if the generator works and updater fails.

• We will have two emails: one for the failure of the updater and one for the error logs.

[leecalcote]

LGTM