Enforce node boundaries in places where it matters

[JacksonKearl]

This just passes "false" explicitly in the places where the behaviour requires no node boundaries. If we were to now flip the default param to 'true', #53182 would be fixed.

[ramya-rao-a]

There are instances of getNode in updateImageSize.ts, mergeLines.ts and util.ts where the no value is passed for the include boundary parameter.
If we are changing defaults, then shouldn't these be updated as well?

I would say that we make this parameter mandatory instead of optional.
This way, when the getNode and getHtmlNode is called, we will know for sure whether we want the boundary included or not

[ramya-rao-a]

On second thoughts, @JacksonKearl like you said, we can also look into including boundaries all the time.
It will need some code changes for the Select Next/Prev Item as well as Balance Out features.
But this would need a thorough testing of all the Emmet features

[JacksonKearl]

Wait I don't think we need to include boundaries all the time (because of the cases like balance in/out and select next/previous). I just think we should flip the default value of the optional parameter to true, or even make it non-optional and change those cases which previously did not pass anything to pass true.