Rebase ENG-8444 splitting main package

[Raj-Dharwadkar]

Rebase ENG-8444 split main package to grpc-server, http-server, and hardware

Description

rebase changes from PR-34 made by kelly deng
Following are changes:
- main package is split into three packages: grpc-server, http-server, and hardware.
- hardware package includes all hardware related i.e, defining hardware structs, getting and exporting data from tink/cacher.

Why is this needed

Fixes: #

How Has This Been Tested?

setup sandbox: build hegel image with these changes and able to provision OS.

How are existing users impacted? What migration steps/scripts do we need?

Checklist:

I have:

• updated the documentation and/or roadmap (if required)
• added unit or e2e tests
• provided instructions on how to upgrade

[codecov]

Codecov Report

Merging #60 (b661098) into master (c8a6831) will increase coverage by 7.09%.
The diff coverage is 26.71%.

@@            Coverage Diff             @@
##           master      #60      +/-   ##
==========================================
+ Coverage   24.40%   31.49%   +7.09%     
==========================================
  Files           5        3       -2     
  Lines         504      381     -123     
==========================================
- Hits          123      120       -3     
+ Misses        359      239     -120     
  Partials       22       22              

Impacted Files	Coverage Δ
grpc-server/grpc_server.go	11.25% <11.25%> (ø)
http-server/http_handlers.go	43.01% <45.00%> (ø)
http-server/http_server.go	50.98% <50.98%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8a6831...b661098. Read the comment docs.

[markjacksonfishing]

Awesome job!

[jacobweinstock]

@Raj-Dharwadkar, this is a great job. Thank you for the time, effort, and energy on this.

Requested changes were handled

[mmlb]

look fine. I imagine it's "better" than what we currently have. it's quite a large PR though with lots of changing/moving parts.

Just for the record:

It does feel like we are trading some current complexities/issues for new ones that should have been avoided. Especially since this is not just a quick and easy split of the main package. Things like removing globals, context propagation, graceful shutdowns should have been discussed as some of the design philosophy for this refactor.

Agreed. I don't think we'd want a full refactor atm though so I think the end result being the same is good for incremental progress. It would have been better if the PR itself wasn't one huge commit and instead was smaller obviously correct changes.