Fix for server translations not working properly (#34)

# Description

Fixes an issue with server translations not working properly

## Type of change

Please mark relevant options with an `x` in the brackets.

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
- [ ] Algorithm update - updates algorithm
documentation/questions/answers etc.
- [ ] Other (please describe):

# How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also
list any relevant details for your test configuration

- [ ] Integration tests
- [ ] Unit tests
- [ ] Manual tests
- [ ] No tests required

# Reviewer checklist

Mark everything that needs to be checked before merging the PR.

- [ ] Check if the UI is working as expected and is satisfactory
- [ ] Check if the code is well documented
- [ ] Check if the behavior is what is expected
- [ ] Check if the code is well tested
- [ ] Check if the code is readable and well formatted
- [ ] Additional checks (document below if any)

# Screenshots (if appropriate):

# Questions (if appropriate):

Author: AlemTuzlak

app/localization/i18n.server.ts

@@ -1,6 +1,6 @@
-import { resolve } from "node:path"
 import { RemixI18Next } from "remix-i18next/server"
 import i18n from "~/localization/i18n" // your i18n configuration file
+import { resources } from "./resource"
 
 const i18next = new RemixI18Next({
 	detection: {
@@ -11,9 +11,7 @@ const i18next = new RemixI18Next({
 	// when translating messages server-side only
 	i18next: {
 		...i18n,
-		backend: {
-			loadPath: resolve("./public/locales/{{lng}}/{{ns}}.json"),
-		},
+		resources,
 	},
 })