Separates tabletop/wallmounted ID authorisation panels (#85124)

## About The Pull Request

We have an ID authorisation panel machine used for things like red
alert, where you need to swipe a card in two different places to
validate it.
_Normally_ this is mounted on a wall in an office, but sometimes it is
on a table. We use the same machine code and sprite for both,

This _mostly_ works but is going to become problematic after the
Wallening.
Resultingly, I've added a sprite and typepath for a desktop version.

![image](https://github.com/user-attachments/assets/10c2828e-53fa-44e0-a2fb-d8f65132f6ae)
Wow! (We need desktop buttons too now that I look at this, I hope the
wallening branch already has that!)

This sprite is secretly the wall-mounted version from the Wallening
(made by Imaginos), but flipped upside down so it looks like it is on a
table not a wall. Delightfully devious (and proposed by "Kok0nut" on
discord).

Also as a result of doing this, I've made wallmounted ID card auth
devices _actually_ attach to the wall in terms of "If the wall goes,
they go too". This may or may not be a good idea given that as far as I
can tell they aren't constructible (and probably shouldn't be given that
then you'd just activate both with one ID card all the time) but seems
broadly sensible to me?

## Why It's Good For The Game

Wallmounted devices should generally deconstruct when associated walls
are destroyed.
Tablemounted devices are going to need different visuals to the
wall-mounted versions.

## Changelog

🆑 Jacquerel, Kok0nut, Imaginos
image: Wall-mounted and Table-mounted ID card authorisation machines now
use different sprites
fix: Wall-mounted ID card authorisation devices will now be destroyed if
their wall is destroyed
/🆑

tools/UpdatePaths/Scripts/85124_wallmounted_id_auth.txt

@@ -0,0 +1 @@
+/obj/machinery/keycard_auth/directional/@SUBTYPES : /obj/machinery/keycard_auth/wall_mounted/directional/@SUBTYPES{@OLD}