Fix eslint warnings in getting-started-typescript app (ref #1095)

[seratch]

Summary

This pull request resolves all the eslint warnings in getting-started-typescript example app project. This is an improvement in addition to #1095

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

Merging #1097 (972c34f) into main (992b64a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1097   +/-   ##
=======================================
  Coverage   69.31%   69.31%           
=======================================
  Files          13       13           
  Lines        1284     1284           
  Branches      380      380           
=======================================
  Hits          890      890           
  Misses        320      320           
  Partials       74       74           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 992b64a...972c34f. Read the comment docs.

[filmaj]

This is great, thanks for doing this.

Related, do we want the main npm run lint task to also lint the example apps?

[seratch]

@filmaj

Related, do we want the main npm run lint task to also lint the example apps?

I think this is a good idea for the TS example app.