feat: Hut Building and game mech (with validation)

[thatchinkumar2005]

--hut spawn from validator.
--dummy data changes.
--hut upgrade changes.
--hut range logic in backend.
--hut side selection logic in backend.
--hut defender validation.
--hut range mechn validation
--new hut defender spawn action type.
--new hut defender spawn response type.
--socket response changes.
--game state changes.

[MegaaDev]

Propsed changes:

• There will be multiple defender_huts, so make that into a vec in state
• Frequency in prop table is the duration of bot coming out of hut in milliseconds not the limit. Store the limit in constants.rs. It must be an object. For each level change the attributes in prop
• Replace if else's in spawn_hut_defender with a function in utils.
• Store last_timestamp field in hut defenders struct. Now check whether the current_time_stamp - last_timestamp >= frequency.
• Dont send the SpawnHutDefender actiontype from frontend, run the timestamp check in attacker_movement and update the defender socket response.
• Follow commit convention.