Fix/device detail respect sort order

[jona159]

Type of Change

• Dependency upgrade
• Bug fix (non-breaking change)
• Breaking change
  • e.g. a fixed bug or new feature that may break something else
• New feature
• Code quality improvements
  • e.g. refactoring, documentation, tests, tooling, ...

Implementation

Checklist

• I gave this pull request a meaningful title
• My pull request is targeting the dev branch
• I have added documentation to my code
• I have deleted code that I have commented out

Additional Information

• This PR closes #

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	70.08%	2134 / 3045
🔵	Statements	68.61%	2204 / 3212
🔵	Functions	68.12%	421 / 618
🔵	Branches	53.8%	1018 / 1892

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
app/db/models/device.server.ts	64.15%	67%	63.41%	64.57%	86-91, 99, 151-152, 221-236, 276, 310, 339, 368, 398, 402, 410-412, 418-420, 438-440, 444-446, 493-647, 698-702, 730-736, 741-757, 836-838, 849, 856-857, 865, 892, 994-1014, 1033
app/db/models/sensor.server.ts	65.9%	66.66%	47.05%	67.44%	70-72, 124-129, 154-220, 274

Generated in workflow #2701 for commit bc1506f by the Vitest Coverage Report Action

[zven]

When a device is freshly created and no order is set, the sensor order in the device settings does not match the tile order:

---

Only after saving the sensor order does their order match in the tile view:

[jona159]

When a device is freshly created and no order is set, the sensor order in the device settings does not match the tile order:

Only after saving the sensor order does their order match in the tile view:

Good catch, should be fixed now