cham projector fixes/rewrite

[deltanedas]

About the PR

• disguise is now just a disguise so if you dont have a hardsuit you can take pressure damage
  fixes Chameleon projector allows you to take no space damage when disguised #27099
• fixed ciggie visualiser so you can disguise as burned and lit ciggies
• cant disguise as things in containers
• finally made it not use polymorph
• fixes Using cham projector as nukie doesnt work #27130

Why / Balance

🐛 🔨

disguising as something in your pocket is cringe like !pch on prop hunt, randomly turn into something that cant be there

Technical details

• an aghost using projector no longer throws
• instead of polymorph, it makes your player invisible and spawns a disguise parented to it.
  being invisible disables verb menu and click attacks but shooting wide swing spacing radiation etc still damage you
• damage revealing is now just based on taking X damage while disguised, instead of a polymorph entity going crit

Media

popup when trying to disguise as something in your pocket/bag/whatever

• I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

no longer uses polymorph, the disguise entity is now just for visuals

Changelog
no cl no fun

[deltanedas]

merg

[deltanedas]

mmmmmmmmmmmmmmmmmmmmerg

[deltanedas]

@mirrorcult merg

[github-actions]

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

[deltanedas]

someone merg this has been running on deltav for ages no issues seal of approval

[AJCM-git]

Aggressively ping me if by next week i haven't come around to this one (in the meantime, do access to the components + l + ratio) (also test with multiple clients and going inside/outside pvs range with em if you havent already) (just saw the deltav testing so you are (prob) guzzy)

[AJCM-git]

This introduces other issues like that the chameleon items dont have interaction outlines and you cant melee them or pick them up, which makes them very easy to spot, also were they always this prone to crashes in debug? i cant fiddle with them for like 5 seconds without getting a client or server crash which is pretty sus.
The general approach is a little odd? It would be better to improve polymorphing to fix the issues it had, tho if you find a way to fix the new issues that isnt jank thats fine too

[github-actions]

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

[deltanedas]

@AJCM-git merg

[github-actions]

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

[Emisse]

is this real

[deltanedas]

yes

[deltanedas]

someone merge already its been like 6 months