Don't ignore error from http.NewRequest

[flimzy]

Description

This PR stops ignoring an error, which lead to a nil pointer dereference in my app:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0xc707bb]

goroutine 1 [running]:
github.com/logzio/logzio-go.(*LogzioSender).makeHttpRequest(0xc0000b48f0, {{0xc0001eaa00, 0x19b, 0x200}, 0x0, 0x0}, 0x0, 0x1)
    /go/pkg/mod/github.com/logzio/[email protected]/logziosender.go:300 +0x19b
github.com/logzio/logzio-go.(*LogzioSender).tryToSendLogs(0xc0000b48f0, 0x0)
    /go/pkg/mod/github.com/logzio/[email protected]/logziosender.go:332 +0xe5
github.com/logzio/logzio-go.(*LogzioSender).Drain(0xc0000b48f0)
    /go/pkg/mod/github.com/logzio/[email protected]/logziosender.go:389 +0x28b
github.com/logzio/logzio-go.(*LogzioSender).Stop(0xc0000b48f0)
    /go/pkg/mod/github.com/logzio/[email protected]/logziosender.go:286 +0x56
gitlab.com/packthathouse/backend.git/internal/slog/logzio.(*Handler).Close(...)
    /app/internal/slog/logzio/logzio.go:74
main.run.func1()
    /app/cmd/backend/backend.go:46 +0x3e
main.run()
    /app/cmd/backend/backend.go:53 +0x59a
main.main()
    /app/cmd/backend/backend.go:27 +0x13

No attempt yet to determine why the request was returning an error. One step at a time, and this looks like an obvious oversight regardless of the root cause.

What type of PR is this?

(check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build / CI
• ⏩ Revert

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help from somebody

[ralongit]

@flimzy Thank you for your contribution, we have merged the changes(#30) in the logzio-go release v1.0.9.