feat: CI Pipeline Notification handling

[Prashant-Microsoft]

Purpose

If deployment fails, it automatically gives the notification to appropriate developers

Does this introduce a breaking change?

• Yes
• No

How to Test

Need to raise the pr, then we have to check the github action workflow

• Test the code
  ensure that your workflow under github action working properly

[github-actions]

Coverage Report •

File	Stmts	Miss	Cover	Missing
code
create_app.py	162	4	97%	336, 454–456
code/backend
Admin.py	23	23	0%	5–9, 11, 13–14, 17, 20–21, 23–24, 27, 35–37, 41, 44–46, 48, 50
code/backend/batch/utilities/helpers
env_helper.py	146	6	95%	249–251, 270–272
code/backend/batch/utilities/helpers/config
assistant_strategy.py	4	0	100%
config_helper.py	157	1	99%	91
code/backend/batch/utilities/helpers/embedders
push_embedder.py	73	0	100%
code/backend/batch/utilities/orchestrator
open_ai_functions.py	54	11	79%	112–114, 117, 120–121, 124, 129–131, 136
code/backend/batch/utilities/tools
question_answer_tool.py	70	0	100%
code/backend/pages
01_Ingest_Data.py	72	72	0%	1–10, 12–14, 16, 24–26, 30, 33–34, 37–40, 42–45, 49–51, 54–56, 59–66, 69–71, 73, 76–79, 82, 87–89, 91–92, 94–95, 98–99, 103–105, 110–113, 120–121, 126, 132–133
04_Configuration.py	154	154	0%	1–10, 12–13, 15, 23–25, 29, 31, 36–45, 48–49, 52–63, 65–68, 70–72, 76–77, 89–93, 96–99, 101–102, 107–108, 112–114, 117–118, 121–122, 125–126, 149, 151–152, 154–158, 160–163, 166–170, 177–178, 188–192, 212–217, 224, 226, 231, 239, 247, 254–255, 262, 264–265, 269, 277, 283, 290, 308–312, 318–319, 338–339, 343, 345–346, 369, 404–405, 409, 412–414, 416, 420–421, 424–427, 429–430, 432–434, 436–439, 441–442
TOTAL	2659	592	77%

Tests	Skipped	Failures	Errors	Time
299	0 💤	0 ❌	0 🔥	40.443s ⏱️

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀