indexing status server

[hopeyen]

• Routes indexing status queries to graph node status endpoint without additional processing
• Fixes query parsing for indexing subgraph and network subgraph queries (remove double parsing of the request)
• Utilizes .toml file parsing for configurations, added example template.toml file
• Adds graceful shutdown
• Adds supported request examples in readme
• Cleans unused dependencies

Resolves #7

Follow up issue #17 to complete the feature

---

I will try to split these up into smaller PRs in the future, kinda got carried away just doing things this time

[github-actions]

Pull Request Test Coverage Report for Build 5739883496

• 0 of 184 (0.0%) changed or added relevant lines in 8 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage remained the same at 0.0%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
service/src/config.rs	0	8	0.0%
service/src/main.rs	0	8	0.0%
service/src/server/routes/network.rs	0	11	0.0%
service/src/util.rs	0	18	0.0%
service/src/server/routes/status.rs	0	19	0.0%
service/src/server/routes/subgraphs.rs	0	22	0.0%
service/src/server/routes/mod.rs	0	25	0.0%
service/src/common/indexer_error.rs	0	73	0.0%

Files with Coverage Reduction	New Missed Lines	%
service/src/server/routes/subgraphs.rs	1	0%

Totals
Change from base Build 5647904549:	0.0%
Covered Lines:	0
Relevant Lines:	1163

---

💛 - Coveralls

[aasseman]

Don't you want to actually respond with the error, instead of panicking and printing the HTTP response?

[aasseman]

.unwrap()s are still there, and will halt the program instead or returning an error HTTP response, or is there something I am misunderstanding?

[hopeyen]

You are right that the program will not return an HTTP response, it will just return curl: (52) Empty reply from server if I do a simple curl with malformed query.
I was trying to avoid the long match/combinator statements, but now I've refactored so that program will return an error HTTP response, think it is much better:)
like this

"Indexer error: IE075, explanation: Failed to parse response body to query string, cause: IndexerErrorCause(FromUtf8Error { bytes: [240, 159, 144], error: Utf8Error { valid_up_to: 0, error_len: None } })

Note: this now outdated iteration of resolver function will indeed lead to a panick thread, but the program will not halt. The server would log something like below and continue serving future requests

thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: (400, Json(FromUtf8Error { bytes: [240, 159, 144], error: Utf8Error { valid_up_to: 0, error_len: None } }))', service/src/server/routes/subgraphs.rs:71:10