Loops and Arrays (03_removeFromArray): Add vanilla/low-level nested loop solution

03_removeFromArray 演習の解答ファイルから始めてください。このファイルには、forEach + includes と filter + includes の解答がすでにあります。あわせて、この演習のテストスイートも確認してください。ネストしたループ版を、コメントアウトした代替案として入れるか、最初の解答として入れるかを決めてから、既存のテストがすべて通ることを確認します。完了の条件は、skip フラグと内側のループについての説明コメントを付けた新しい解答が存在し、03_removeFromArray のテストがこれまでどおり通ることです。

Prerequisites

• I have thoroughly read and understand The Odin Project Contributing Guide
• I have searched the existing issues to ensure this improvement hasn't been suggested before (please have a look through our open issues list to make sure)
• The title of this issue follows the <Location of the improvement>: <Brief description of the improvement> format, e.g. Exercises: Add exercise on XYZ
• (Optional) I am interested in working on this issue and would like to be assigned to it

Improvement Description

I would like to propose adding a third, "vanilla/low-level" solution to the 03_removeFromArray exercise.
Currently, the file provides two solutions: one using .forEach() + .includes(), and a more advanced one using .filter() + .includes(). While these are great, both rely on high-level built-in methods (.includes).
Adding an imperative solution using nested loops and a flag would be highly beneficial for beginners. It demonstrates how array filtering works "under the hood" at a foundational level using only basic language constructs (for...of, conditions, and flags) without relying on any built-in lookup methods.

Acceptance Criteria

• Add the nested loops solution as an alternative commented-out approach or as the initial basic approach in the solutions file.
• Ensure the solution passes all existing test suites for 03_removeFromArray.
• Provide clear code comments explaining the algorithmic logic (e.g., the purpose of the skip flag and the inner loop breakdown).

(Optional) Additional Comments

Here is the proposed implementation for the additional solution:

const removeFromArray = function (arr, ...toDelete) {
  const deletedArr = [];
  
  for (const elementArr of arr) {
    let skip = false;

    // Manually checking for inclusion without using .includes()
    for (const elementDelete of toDelete) {
      if (elementArr === elementDelete) {
        skip = true;
        break; // Stop looking if a match is found
      }
    }

    // Only push if the element was not flagged for deletion
    if (!skip) deletedArr.push(elementArr);
  }
  
  return deletedArr;
};

Use code with caution.
This approach helps students strengthen their algorithmic thinking and mental models before they fully transition to abstract methods like .filter().