Decompile foreground and bones (#3427)

Small fix to decompiler when the original compiler uses `ra` register.
This seems to happen in "normal" code very rarely - perhaps they
manually specified this in an `rlet`.

Start figuring out buckets/textures for Jak 3.

The foreground code is not yet modified for PC - I want to wait until
the game is running, since it is too hard to do it now.

decompiler/analysis/atomic_op_builder.cpp

@@ -162,7 +162,7 @@ std::unique_ptr<AtomicOp> make_standard_load(const Instruction& i0,
                                              int idx,
                                              int load_size,
                                              LoadVarOp::Kind kind) {
-  if (i0.get_dst(0).is_reg(rra()) || i0.get_dst(0).is_reg(Register(Reg::GPR, Reg::SP))) {
+  if (i0.get_dst(0).is_reg(Register(Reg::GPR, Reg::SP))) {
     return std::make_unique<AsmOp>(i0, idx);
   }
   auto dst = make_dst_var(i0, idx);

decompiler/config/jak2/all-types.gc

@@ -7820,7 +7820,7 @@ In some cases, the return value is checked for `'dead`."
   :flag-assert         #xe00000020
   ;; field param1 uses ~A with a signed load field param2 uses ~A with a signed load field param3 uses ~A with a signed load
   (:methods
-    (get-engine 
+    (get-engine
       "Get the engine for this connection. This must be used on a live connection." (connection) engine) ;; 9
     (get-process "Get the process for this connection." (connection) process) ;; 10
     (belongs-to-engine?
@@ -22432,7 +22432,7 @@ Levels store a reference to this which holds all the entities in the level."
 
 (deftype entity (res-lump)
   "Entities are mainly used to place objects in a level.
-  
+
   As a child of [[res-lump]], they store various types of metadata
   in [[res-tag]]s (such as name, curve data, volume data, etc.)
   that gets accessed by the accompanying process."