Implement Sandbox notifications processor and publisher

[Future-Outlier]

TL;DR

Implement notifications processor and publisher for Sandbox.

Type

• Bug Fix
• Feature
• Plugin

Are all requirements met?

• Code completed
• Smoke tested
• Unit tests added
• Code documentation added
• Any pending items have an associated Issue

Complete description

Add new SandboxProcessor and SandboxPublisher that implement the Processor interface.

I add config in yaml file like this

notifications:
  type: sandbox
  emailer:
    emailServerConfig:
      apiKeyEnvVar: "SENDGRID_API_KEY"
    subject: "Notice: Execution \"{{ name }}\" has {{ phase }} in \"{{ domain }}\"."
    sender: "example@gmail.com"  # Consider using a generic email instead of personal
    body: >
      Execution \"{{ name }}\" has {{ phase }} in \"{{ domain }}\". View details at
      <a href=\http://example.com/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}>
      http://example.com/projects/{{ project }}/domains/{{ domain }}/executions/{{ name }}</a>. {{ error }}

screenshot

Tracking Issue

Remove the 'fixes' keyword if there will be multiple PRs to fix the linked issue

fixes https://github.com/flyteorg/flyte/issues/

Follow-up issue

NA
OR
https://github.com/flyteorg/flyte/issues/

[codecov]

Codecov Report

Merging #595 (3721b9c) into master (04bcb15) will increase coverage by 1.84%.
The diff coverage is 100.00%.

❗ Current head 3721b9c differs from pull request most recent head 19aef7f. Consider uploading reports for the commit 19aef7f to get more accurate results

@@            Coverage Diff             @@
##           master     #595      +/-   ##
==========================================
+ Coverage   58.42%   60.26%   +1.84%     
==========================================
  Files         168      170       +2     
  Lines       16393    13433    -2960     
==========================================
- Hits         9578     8096    -1482     
+ Misses       5964     4486    -1478     
  Partials      851      851              

Flag	Coverage Δ
unittests	?

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

Files Changed	Coverage Δ
pkg/async/notifications/factory.go	19.07% <100.00%> (+14.62%)	⬆️
...notifications/implementations/sandbox_processor.go	100.00% <100.00%> (ø)
...notifications/implementations/sandbox_publisher.go	100.00% <100.00%> (ø)

... and 154 files with indirect coverage changes

[Future-Outlier]

@pingsutw I've updated my test, please check it.
Also to use the mock emailer int test function, I've added a "return nil" in my sandbox_processor.go.
Thanks a lot.

[Future-Outlier]

I am not pretty sure whether use a noop emailer or a mock emailer, please get in touch with me if it is necessary to change the code.
Thanks a lot.

[Future-Outlier]

BTW, I just copy the master branch's go.mod and go.sum to my branch currently and run "go mod tidy"
I found that it is not needed to update the go.mod and go.sum.
Thanks a lot

[katrogan]

Looks great. This is failing the code coverage check, but I think the code cov annotations have suggestions for some additional test cases we could use to bump the code coverage on this PR and so that we can test more scenarios

[Future-Outlier]

Looks great. This is failing the code coverage check, but I think the code cov annotations have suggestions for some additional test cases we could use to bump the code coverage on this PR and so that we can test more scenarios

Thanks for the suggestions, I've learned a lot!

[katrogan]

Thank you for adding all the unit tests!