Fix some type issues in tilemap module

[dumganhar]

Re: #

Changelog

---

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

---

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

[github-actions]

👍 Package size ⤵ -63 bytes, old: 5225108, new: 5225045

Interface Check Report

This pull request does not change any public interfaces !

[minggo]

data is TiledSubNodeData: What does this code mean?

[dumganhar]

It's similar with the PR #18264
Basically, this is a typescript syntax that if the function returns true, then the data is a TiledSubNodeData type. This could avoid type convertion in if logic. For example:

class Base {
}

class TiledSubNodeData extends Base {
   hello();
}

const pBase: Base = new TiledSubNodeData();

if (isTiledSubNodeData(pBase)) { // pBase is Base type, but it's an instance of TiledSubNodeData, so this function return true. And pBase will be treated as a TiledSubNodeData instance.

    pBase.hello(); // No need to convert it to TiledSubNodeData by `(pBase as TiledSubNodeData).hello();`

}

[dumganhar]

See: https://matiashernandez.dev/blog/post/what-are-type-predicates-in-typescript

[dumganhar]

[minggo]

Got it, thanks.

[dumganhar]

@cocos-robot run test cases