[core, sql] Status effect wear off messages, ON_ZONE flags

[sruon]

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?

• Adds a new column to override the wear off message for status effects
  • After going through the motions I'm not even sure it was required to begin with because everything is either message 204 or 206 but might be useful later on...
• Adds the correct message ID for certain status effects wearing off
  • Tested what I could myself, used Youtube videos for a few and made some assumptions about a limited number. Likely not ENTIRELY accurate.
• Defines the flags explicitly in the SQL file
• Adds ON_ZONE flag to a lot of status effects
  • As captured by @siknoz
  • Skipped everything that said "N/A" in the retail column for the time being
• Sets the correct "caster" entity in the wear off message, as observed on retail
  • Makes no visual difference but I don't think filters can work correctly otherwise.

Maybe closes #8898 - need another pass

Steps to test these changes

[almuth150]

I just noticed that this status has no flags. I checked with a test server and couldn't manually remove the status with the client normally, so maybe this status should have the no cancel flag? I can't check on retail though. But surely the status that prevents you from using certain powerful meds repeatedly shouldn't be able to be removed by the player.

Edit: It looks like there are more statuses that lack that flag, so I'm going to open a separate issue. Ignore this for this PR.