feat: status endpoints

[plyr4]

implements go-vela/community#749 in a way that doesnt impact current status svg responses.

instead, two new endpoints to get unauthenticated access to "lite" versions of repo and builds.

Concerns

• potential impact to the database from unauthenticated and untrackable spam. but... this is not a new problem. could easily do it elsewhere (dashboards, pat auth, etc) if you were determined, but still.
• the /badge endpoint for "private repos" have never been protected, but this is obviously opening the door much wider.

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 38 lines in your changes missing coverage. Please review.

Project coverage is 56.60%. Comparing base (4c9e836) to head (e42c378).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
api/build/status.go	0.00%	11 Missing ⚠️
api/repo/status.go	0.00%	11 Missing ⚠️
api/types/build.go	0.00%	7 Missing ⚠️
router/router.go	0.00%	6 Missing ⚠️
api/types/repo.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1235      +/-   ##
==========================================
- Coverage   56.66%   56.60%   -0.06%     
==========================================
  Files         626      628       +2     
  Lines       35541    35578      +37     
==========================================
  Hits        20139    20139              
- Misses      14722    14759      +37     
  Partials      680      680              

Files with missing lines	Coverage Δ
api/types/repo.go	99.17% <0.00%> (-0.83%)	⬇️
router/router.go	0.00% <0.00%> (ø)
api/types/build.go	97.56% <0.00%> (-1.06%)	⬇️
api/build/status.go	0.00% <0.00%> (ø)
api/repo/status.go	0.00% <0.00%> (ø)

[wass3rw3rk]

test fail. swagger annotation is defining GetStatus twice. otherwise 👍🏼

[wass3rw3rk]

what do you think about dropping email from the build status endpoint at least? maybe deploy_payload, as well.