Refactor inventory and item equip flow

[MelonChicken]

Summary

While verifying user flow (manual end-to-end test), I found several issue.

• reflected actual assets in the front
• Fixed inventory retrieval to handle async item lookup correctly using a for loop
• Updated item equip logic to apply and remove item effects properly
• Improved shop purchase response to return updated user item and will balance

Changes

• authService.js

  • Replaced async forEach with for loop in getInventory
  • Ensures item lookup is awaited correctly

• eggService.js

  • Applies new item effect when equipping
  • Removes previous item effect when replacing equipped item

• shopService.js

  • Returns created/updated user item info
  • Returns current will balance after purchase

Test

• Checked inventory retrieval after purchase
• Checked equip behavior when replacing already equipped items
• Follow the user flow (Register -> Login -> post -> shop -> egg) in Swagger UI

How to test

• After deleting database, re-initialize using npm install and npm start

[naviGateauR]

Looks all good to me. I can see the changes in the code align with the documentation on SwaggerUI.

I was also able to test both the GET and POST endpoint of the Shop.
No issues.

There is a conflict with the database.sqlite though. How do we want to resolve it ?
user the one from the main branch and not merge it ?

[MelonChicken]

Looks all good to me. I can see the changes in the code align with the documentation on SwaggerUI.

I was also able to test both the GET and POST endpoint of the Shop. No issues.

There is a conflict with the database.sqlite though. How do we want to resolve it ? user the one from the main branch and not merge it ?

I can we can just delete database from this branch