[Monorepo] Update manifest using the monorepo components

[eapolinario]

Describe your changes

This PR changes the generation of manifests to use the versions of components in the monorepo.

A few things to note:

1. This process relies on the fact that changes to components trigger the creation of tags once they are merged to master. This essentially means that two consecutive releases are not supported since component tags are only generated once changes to components are merged to master. We might need to relax this constraint and assume that all merges to master produce component tags.
2. In order to generate the config docs we no longer download component binaries from releases, instead we compile them in place.
3. The release process described in https://github.com/flyteorg/flyte/blob/master/RELEASE.md#create-a-release stays unchanged.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (8090b16) 58.95% compared to head (397cd71) 59.26%.

❗ Current head 397cd71 differs from pull request most recent head 8a97a37. Consider uploading reports for the commit 8a97a37 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4082      +/-   ##
==========================================
+ Coverage   58.95%   59.26%   +0.30%     
==========================================
  Files         618      549      -69     
  Lines       52676    39581   -13095     
==========================================
- Hits        31057    23459    -7598     
+ Misses      19140    13807    -5333     
+ Partials     2479     2315     -164     

Flag	Coverage Δ
unittests	?

Flags with carried forward coverage won't be shown. Click here to find out more.

see 555 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.