[Job Utils] Bluemage job abilities

[andeluvian]

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?

This PR contains the jobutils for Blue Mage, jobabilities have been moved not to jobutils

Steps to test these changes

Create a new player with blue mage job either 75 or 99 and each ability should work as they did before the change.

[zach2good]

As a general rule: your commit messages should say what your piece of work is doing in relation to the codebase.

If you introduce some code in an early commit, and then change the formatting (etc.) in a later commit, that's got no relevance to the codebase, it's specific to your code - so squash it please.

Commits as atomic pieces of work, etc.

[zach2good]

https://github.com/LandSandBoat/server/wiki/Development-Guide-Git#writing-useful-commit-messages

[zach2good]

While you're doing these PRs, the ability use binding should always have the action param, even if it isn't used:

abilityObject.onUseAbility = function(player, target, ability, action)
    return xi.job_utils.rune_fencer.useBattuta(player, target, ability, action)
end

etc.

It can safely be omitted, because Lua, but Core is piping it in, so it should be shown in case people want/need it later

[zach2good]

https://github.com/LandSandBoat/server/blob/base/src/map/lua/luautils.cpp#L4201

[zach2good]

Seems fine to me, just needs work so CI doesn't complain