Circumvented Deprecated API Call / Invalid Arg Error

[Bitwise1057]

Replaced UnitBuff with C_TooltipInfo.GetUnitBuff, since UnitBuff has been deprecated.
Resolved error:
Message: ...nterface/AddOns/CameraOverShoulderFix/correction.lua:297: attempt to call upvalue 'UnitBuff' (a nil value)

Patched an issue with the mount journal API that repeatedly threw:

Message: bad argument #1 to '?' (Usage: local name, spellID, icon, isActive, isUsable, sourceType, isFavorite, isFactionSpecific, faction, shouldHideOnChar, isCollected, mountID, isSteadyFlight = C_MountJourn...)
This error prevented the camera from resetting correctly after dismounting.

Added API checks and error handling as a temporary workaround until a proper fix is in place.

These changes should stop the addon from throwing runtime errors in current builds while maintaining functionality.

[LudiusMaximus]

Sorry I left you PR unanswered for so long. Maybe @Shushuda can take it from here... :-)

[Shushuda]

Oops, I think I might have fixed those two errors in these commits today hahaha

b657a15
12aa842

The proper replacement for the UnitBuff (which was an alias for UnitAura(unit, index, "HELPFUL") ) is C_UnitAuras.GetBuffDataByIndex, hence why I replaced it with that.

As for the other one, my debugging seemed to always land in that one spot with force dismount due to lastActiveMount being nil, hence why the fix is just an if-statement wrap. Seems to work for Soar (which I could reproduce), but I haven't encountered this bug on regular dismounting.
Was Message: bad argument #1 to '?' happening on regular mounts too? Do you have the full error printout from BugSack, including Locals at the bottom? That would be very helpful.

[Bitwise1057]

I'll have to look into it when I get the chance. I do not currently have the full printout as it has been a few months since I was working with this and changes with the API may have had some manner of impact since then.