Refactor Gist Web to use Fetch API

[stephen-pope-customer-io]

To replace axios

Part of INAPP-12465
Part of INAPP-13292

[Copilot]

Pull Request Overview

This PR refactors the network service to replace axios with the Fetch API, streamlining network requests for the Gist Web application.

• Replaces axios with the Fetch API and AbortController for timeouts.
• Reorganizes baseURL selection and header construction based on API version and user token.
• Implements a POST helper function with JSON serialization.

Comments suppressed due to low confidence (1)

src/services/network.js:49

• [nitpick] Consider wrapping the thrown error in an instance of Error (e.g., new Error(...)) to preserve the stack trace and ensure consistent error handling.

throw {

[mvanderlinde]

Just a couple opportunities for simplification, but nothing blocking from my perspective. 👌

[mvanderlinde]

💡 This could be simplified by using the ok Response attribute.

Suggested change

	if (response.status < 200 || response.status >= 400) {
	if (!response.ok) {

[BernardGatt]

I think its because we also need to handle 304s.

[stephen-pope-customer-io]

Bernard is correct, we return a 304 Not Modified when users hit the cache for messages instead of going to Firestore.

[jefago]

does this mean that the dependency on axios can be removed? it doesn't seem to be used anymore, and the referenced version has a CVE vulnerability axios/axios#6463

[stephen-pope-customer-io]

does this mean that the dependency on axios can be removed? it doesn't seem to be used anymore, and the referenced version has a CVE vulnerability axios/axios#6463

Yes, I have opted to refactor using fetch api instead of updating axios.

[jefago]

Thank you! Will there be a new release without the axios dependency (since it's still referenced in the package.json right now)?

[stephen-pope-customer-io]

Ah, yes, of course! I will remove the dependency and release again.

[jefago]

Thank you!