refactor: refactor unnecessary else / elif when if block has a …

…`return` statement

The use of `else` or `elif` becomes redundant and can be dropped if the last statement under the leading `if` / `elif` block is a `return` statement.
In the case of an `elif` after `return`, it can be written as a separate `if` block.
For `else` blocks after `return`, the statements can be shifted out of `else`. Please refer to the examples below for reference.

Refactoring the code this way can improve code-readability and make it easier to maintain.

model-gym-ros-env/car_node/car_node/wrapper.py

@@ -102,8 +102,7 @@ def start_position(self):
             x, y, t = map_utility.get_start_position(self.map_path)
             self.set_raceliens()
             return x, y, t
-        else:
-            raise Exception("Map path not set")
+        raise Exception("Map path not set")
 
 
 

src/wrapper/wrapper.py

@@ -115,8 +115,7 @@ def start_position(self):
             x, y, t = map_utility.get_start_position(self.map_path)
             self.set_raceliens()
             return x, y, t
-        else:
-            raise Exception("Map path not set")
+        raise Exception("Map path not set")