Add additional safety, logging to CLuaBaseEntity bindings

[claywar]

I affirm:

• I understand that if I do not agree to the following points by completing the checkboxes my PR will be ignored.
• I understand I should leave resolving conversations to the LandSandBoat team so that reviewers won't miss what was said.
• I have read and understood the Contributing Guide and the Code of Conduct.
• I have tested my code and the things my code has changed since the last commit in the PR and will test after any later commits.

What does this pull request do?

Searches existing code in lua_baseentity.cpp for static_cast<CBattleEntity*> and audits existing code for appropriate checks, since NPCs can potentially call these functions and cause failures.

If NPC check is currently existing, code is not modified, but if no check exists, it converts to dynamic_cast. In some cases, types were modified to reflect the expected function (ex: CCharEntity* being passed into CBattleEntity* parameter)

Steps to test these changes

Check expected result from valid target(s), attempt to call function on NPC to see error messaging and no crash

[claywar]

I'd say in this case it more exposes another issue now that logging exists. The following function expects CCharEntity, and we're stuffing some other type into it somewhere. Most likely the underlying battleutils function needs to be audited, along with our usage of it in general:

[claywar]

Correct since it will bail out of the function on that warning. Should be resolved by #6652