In build.gradle, the dependencies on distZip and/or distTar causes
the shadowJar task to generate a second JAR file for which the
mainClass.set("seedu.duke.Duke") does not take effect.
Hence, this additional JAR file cannot be run.
For this product, there is no need to generate a second JAR file
to begin with.

Let's remove this dependency from the build.gradle to prevent the
shadowJar task from generating the extra JAR file.

# Conflicts:
#	src/main/java/mysutong/Storage.java

# Conflicts:
#	src/main/java/mysutong/Parser.java
#	src/main/java/mysutong/Ui.java

The executeCommand method in Parser handles user commands by splitting the input string into two parts: the command itself and any additional arguments.

Currently, the split operation does not validate that the input string contains at least one element, which could potentially lead to unexpected behaviour or bugs if empty input is passed.

To mitigate this, let's add an assert statement to ensure that the inputs array has at least one element. This ensures that the code always receives a valid command to process. In situations where assertions are enabled, this will help catch empty or invalid commands during development and testing.

While this doesn't address user input validation directly (since assert can be disabled in production), it adds an extra layer of safety during development.

This change also avoids unnecessary array access errors and improves the stability of the command handling logic.

This commit refactors the code to conform to the Checkstyle configuration, ensuring consistency and compliance with coding standards.

Changes made:
- Replaced wildcard imports (e.g., import static org.junit.jupiter.api.Assertions.*) with explicit imports for better clarity and to avoid unnecessary imports.
- Corrected import order to follow the standard conventions, ensuring that java.* imports are grouped together and listed alphabetically.
- Fixed spacing issues, such as ensuring a single space between comments and code, and after operators (e.g., =, +).
- Improved overall code readability and conformance to Checkstyle rules by addressing minor formatting inconsistencies.

These changes are intended to improve the maintainability of the codebase by ensuring that it follows consistent styling rules as enforced by Checkstyle. By doing this, we minimize the chances of formatting-related errors and enhance code readability across the project.

All changes are purely stylistic and do not alter the functionality of the code.

Add assertion to ensure valid command input

Refactor code style to adhere to Checkstyle guidelines