[JS] feat: add helper functions to to get Teams channels, members, and details

[yiqing-zhao]

Linked issues

closes: #minor

Details

Provide a list of your changes here. If you are fixing a bug, please provide steps to reproduce the bug.

Change details

We have encapsulated three APIs from TeamsInfo class of botbuilder library: getTeamChannels, getTeamDetails, and getPagedMember, to facilitate easier proactive message sending. These three APIs have been wrapped as an initial sample. If this approach is deemed acceptable, we intend to extend this encapsulation to include additional APIs provided by TeamsInfo, such as sendMessageToListOfUsers, sendMessageToAllUsersInTenant, and more.

PM Contact: @MuyangAmigo

code snippets:
To use the APIs:

for (const reference of conversationReferences) {
  await app.sendProactiveActivity(
    reference,
    "Proactive message from RestifyNotiBot!"
  );

  if (reference.conversation?.conversationType === "channel") {
    const details = await app.getTeamDetails(reference);
    const teamMembers = await app.getPagedMembers(reference);
    console.log(details, teamMembers.members.length);
  }
}

screenshots:
Results are printed as belows, furthur

Attestation Checklist

• My code follows the style guidelines of this project

• I have checked for/fixed spelling, linting, and other errors

• I have commented my code for clarity

• I have made corresponding changes to the documentation (updating the doc strings in the code is sufficient)

• My changes generate no new warnings

• I have added tests that validates my changes, and provides sufficient test coverage. I have tested with:

  • Local testing
  • E2E testing in Teams

• New and existing unit tests pass locally with my changes

Additional information

Feel free to add other relevant information below

[corinagum]

could you also add unit tests for the new code? thanks!

[yiqing-zhao]

could you also add unit tests for the new code? thanks!

Thanks @corinagum, some unit tests are added for the codes. Please help to review, thanks!

[corinagum]

@yiqing-zhao Thank you! Internally we are discussing some structural strategies that would affect these changes so this PR may not be merged immediately until we finalize on those decisions. We might need to iterate on your changes before merge as well, but we appreciate the contribution! I'll update this thread as more information becomes available.

[MuyangAmigo]

@yiqing-zhao Thank you! Internally we are discussing some structural strategies that would affect these changes so this PR may not be merged immediately until we finalize on those decisions. We might need to iterate on your changes before merge as well, but we appreciate the contribution! I'll update this thread as more information becomes available.

Hey @corinagum have those discussions been finalized?