feat(no-topromise): suggest an exact replacement for toPromise()

[JasonWeinzierl]

This adds the "most correct" suggestion to no-topromise for replacing toPromise().

The old toPromise() would resolve to undefined, while the new lastValueFrom rejects with EmptyError. So if a user followed the old top suggestion and replaced toPromise with lastValueFrom, they might be surprised to find EmptyError now thrown instead. This wouldn't be a problem for someone using the strict config, which includes no-ignored-default-value, but users of the recommended config wouldn't get that lint notification.

Resolves #168

[github-actions]

LCOV of commit 4f2ecf5 during .github/workflows/ci.yml #477

Summary coverage rate:
  lines......: 96.7% (4333 of 4479 lines)
  functions..: 96.1% (270 of 281 functions)
  branches...: no data found

Files changed coverage rate:
                                         |Lines       |Functions  |Branches    
  Filename                               |Rate     Num|Rate    Num|Rate     Num
  =============================================================================
  src/rules/no-topromise.ts              | 4.0%    100| 0.0%     4|    -      0