feat(authentication): add support to persist sessions and flows in database

[Chief-Rishab]

• Add support to save user sessions and flows in the postgres database
• Documentation
  • Update API and CLI reference
  • Update server configurations

[coveralls]

Pull Request Test Coverage Report for Build 4691795498

• 0 of 208 (0.0%) changed or added relevant lines in 6 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-1.2%) to 54.821%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
cmd/serve.go	0	2	0.0%
internal/api/v1beta1/authenticate.go	0	2	0.0%
internal/store/postgres/session.go	0	9	0.0%
internal/store/postgres/flow.go	0	10	0.0%
internal/store/postgres/flow_repository.go	0	89	0.0%
internal/store/postgres/session_repository.go	0	96	0.0%

Totals
Change from base Build 4665802449:	-1.2%
Covered Lines:	4702
Relevant Lines:	8577

---

💛 - Coveralls

[kushsharma]

@Chief-Rishab can you rebase this with main, I'll review it after

[Chief-Rishab]

@kushsharma this PR is ready for review now

[kushsharma]

instead of varchar can we use text

[Chief-Rishab]

isn't VARCHAR and TEXT same if we don't specify the number to limit the characters?

https://www.postgresqltutorial.com/postgresql-tutorial/postgresql-char-varchar-text/#:~:text=Different%20from%20other%20database%20systems,to%20check%20for%20the%20length.

[kushsharma]

Yes they are same, I thought in rest of the migrations we are using text so I thought we may want to keep it consistent, I just checked looks like we actually use varchar. Should be fine then.