Make creature's "moves" a protected variable

[RenechCDDA]

Summary

None

Purpose of change

Magic numbers bad

Accessing a creature's moves directly, also bad

Describe the solution

Replaced some instances of other arbitrary valuations with calculations for fractions of get_speed() that matched the previous numbers, assuming speed == 100

Actions which were related to the character performing a task use get_speed() to calculate their new time. Actions which were related to things happening (e.g. interacting with a computer) calculate their new move cost in seconds. For creatures with speed of == 100 (and indeed, most of these are just hardcoded player actions) there is no functional change.

Describe alternatives you've considered

Testing

Compiles 👍

Reviewers are advised to scrutinize the monster files in particular... my best effort was made to make sense of what was going on in there but I annotated at least two places where functionality has changed. Previous behavior of modifying monster moves' by flat value assumed to be a bug.

Additional context

[mqrause]

Still plenty of unguarded access to creatures' moves.

I'd recommend making the member protected and then fixing all the errors at once.

[RenechCDDA]

Still plenty of unguarded access to creatures' moves.

I'd recommend making the member protected and then fixing all the errors at once.

What, and make more work for myself? Fine, fine. Reason wins again.

[github-actions]

Auto-requesting reviews from non-collaborators: @wapcaplet

[Fris0uman]

A few notes on some potential errors of conversion