[WIP] Improving Initial Load for Participant Selector in BSDT

[abalimane]

…o scoped notification to show when limit is exceeded

Critical Changes

Changes

• Added info scoped notification to show when there are too many records to show
• Added limit for the number of program engagements to show (set to 1000)

Issues Closed

New Metadata

Deleted Metadata

Definition of Done

Refer to Asteroids DoD document to see any additional details for the items below

• Any net new LWC work has Sa11y tests & 50% or above lines JEST test coverage
• CRUD/FLS is enforced in Apex
• Permission sets are updated to account for CRUD|FLS|Tab|Classes
• Field sets are updated to account for new fields
• UX approval or UX not necessary
• Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name (Reorganize code; use custom iterator #303)
• All acceptance criteria have been met
  • Developer
  • Code Reviewer
  • QA
• PR contains draft release notes
• QE story level testing completed

[abalimane]

TODO: Get Message to put into the info scoped notification for when there are more engagements than the limit

[salesforce-cla]

Thanks for the contribution! It looks like @abalimane is an internal user so signing the CLA is not required. However, we need to confirm this.