fix: replace wrong rows when use setRows API with filter

[jajugoguma]

Please check if the PR fulfills these requirements

• It's submitted to right branch according to our branching model
• It's right issue type on title
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes/features)
• Docs have been added/updated (for bug fixes/features)
• It does not introduce a breaking change or has description for the breaking change

Description

• Fixed an issue where using the setRows API when filtering would change the wrong row and create duplicate rows.
  • It was caused by looking for the row index of the row to be changed in unfiltered data and finding the wrong row index.

As-Is

To-Be

---

Thank you for your contribution to TOAST UI product. 🎉 😘 ✨

[sunyoungBae]

대부분의 변경사항에 동의합니다.
테스트 쪽에 사소한 리뷰 몇개 추가했습니다. 주요 로직에 영향을 끼치진 않으므로 바쁘시면 변경하지 않으셔도 됩니다.