When resolving type reference directive use baseUrl and other resolution settings

[sheetalkamat]

This one ensures that we resolve type reference directive with baseUrl since #32878 started using baseUrl considerations to generate ///<reference types instead of ```///<reference path` and accounting for baseUrl

This is one possible fix for the issue wherein we use baseUrl when resolving type reference name.
Other could be to generate ///<reference path when file is referenced only throught ```//reference path` and relative import path tree from root file.
Possibly Fixes #37928

[sheetalkamat]

@RyanCavanaugh @weswigham @DanielRosenwasser can you please comment on what you think is better approach.
As mentioned in the description the declaration emit prefers type reference directive over reference path and uses baseUrl to determine that portion. But our type reference directive resolution doesnt use baseUrl.

Does declaration emit need to be better (use relative paths when file is referenced through tree of relative paths.. Old branhc for this which doesnt handle tree case https://github.com/microsoft/TypeScript/compare/experimentRelativePaths ) or resolution which this PR tries to fix?

[weswigham]

I think we should, generally speaking, strive to make declaration emit use "the most portable" paths for things (certainly, emitting things which only work with a specific compiler option configuration isn't very portable).

[timocov]

Shouldn't it be reference path instead? How <reference types="types" /> will be resolved by another project referencing to this one? I mean, afaik reference types means "load types from types-like package (from both typesRoot or node_modules/@types) with specific name", but this is the local file, why we should refer to it with types instead of path?