Changes Runner bone spur ability to use get_turf() instead of locate().

[Venuska1117]

Detached from: #12601

About the pull request

replaces locate() with get_turf()

Explain why it's good for the game

Update code, better logic.

Testing Procedure

Made new code, run code, no errors.
spawn runner, use bone spur, bone spur work fine.

Code works as intended.

Changelog

🆑 Venuska1117
refactor: Changes Runner bone_spur code to use get_turf() instead of locate().
/:cl:

[fira]

why put it in this file?

[Venuska1117]

why put it in this file?

stuff from _powers.dm should be moved to other files, we already have runner.dm and runner_abilities.dm spreading to more files like runner_powers.dm is confusing.

This changes are also in this PR, this one moves most powers.dm to their respective files to decrease bloat. (could make reviewing this code easier if it was merged)
#12607

[cmss13-ci]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

[cm13-github]

This pull request has conflicts, please resolve those before we can evaluate the pull request.

[cm13-github]

Conflicts have been resolved. A maintainer will review the pull request shortly.

[cmss13-ci]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

no longer applicable