API update for selection change

[IanMatthewHuff]

For #5515

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• Title summarizes what is changing.
• Has a news entry file (remember to thank yourself!).
• Appropriate comments and documentation strings in the code.
• Has sufficient logging.
• Has telemetry for enhancements.
• Unit tests & system/integration tests are added/updated.
• Test plan is updated as appropriate.
• package-lock.json has been regenerated by running npm install (if dependencies have changed).

[IanMatthewHuff]

I pulled in just the selection change here. Pulling in the file was bringing in more kernel deprecations that I'd rather deal with the kernel push work.

@DonJayamanne Side note, we seem to have always had three copies of this file. Can we condense down to one? Wasn't sure if there was a reason for the copies, so I didn't do that in this PR.

[DonJayamanne]

I don't recall why we had 3, possibly something from core extension. Or maybe when we were using ts-node or the like...
Please do feel free to remove the duplicates.

[IanMatthewHuff]

@DonJayamanne sounds good. Will do with kernel API update.