refactor(frontend): update multichannel route to include case Id parameter

[faiza-jahanzeb]

Summary

update multichannel route to include case Id parameter

Types of changes

What types of changes does this PR introduce?
(check all that apply by placing an x in the relevant boxes)

• 🛠️ refactoring -- non-breaking change that improves code readability or structure
• 🐛 bugfix -- non-breaking change that fixes an issue
• ✨ new feature -- non-breaking change that adds functionality
• 💥 breaking change -- change that causes existing functionality to no longer work as expected
• 📚 documentation -- changes to documentation only
• ⚙️ build or tooling -- ex: CI/CD, dependency upgrades

Checklist

Before submitting this PR, ensure that you have completed the following. You can fill these out now, or after creating the PR.
(check all that apply by placing an x in the relevant boxes)

• code has been linted and formatted locally
• added or updated tests to verify the changes
• added adequate logging for new or updated functionality
• ensured metrics and/or tracing are in place for monitoring and debugging
• documentation has been updated to reflect the changes (if applicable)
• linked this PR to a related issue (if applicable)

Linting and formatting

npm run lint:check
npm run format:check

Unit and e2e tests

npm run test
npm run test:e2e

Additional Notes

If this PR introduces significant changes, explain your reasoning and provide any necessary context here. Feel free to include diagrams, screenshots, or alternative approaches you considered.

Screenshots (if applicable)

Provide screenshots or screen-recordings to help reviewers understand the visual impact of your changes, if relevant.

[sebastien-comeau]

Is it possible to place :caseId after /multi-channel? That would make more sense since it's a subflow within a specific case.

For example: /multi-channel/:caseId/search-sin/

[gregory-j-baker]

Is it possible to place :caseId after /multi-channel? That would make more sense since it's a subflow within a specific case.

For example: /multi-channel/:caseId/search-sin/

If we want to follow the resource-identification convention for URLs, a better name might be /cases/:caseId/{sub-resouce} because you're pulling the case data associated with caseId.

🤷🏻

[sebastien-comeau]

If we want to follow the resource-identification convention for URLs, a better name might be /cases/:caseId/{sub-resouce} because you're pulling the case data associated with caseId.

You're suggesting something like /cases/:caseId/multi-channel/search-sin/?

[sebastien-comeau]

👍

Next, find sin case using caseId params in each loaders and actions of multi-channel routes.

// TODO ::: GjB ::: the data returned by the following call should be checked to ensure the logged-in user has permissions to view it
const sinCase = await getSinCaseService().findSinCaseById(params.caseId);

if (sinCase === undefined) {
  throw new Response(JSON.stringify({ status: HttpStatusCodes.NOT_FOUND, message: 'Case not found' }), {
    status: HttpStatusCodes.NOT_FOUND,
  });
}