feat: glee authentication using auth directory

[oviecodes]

Description
This PR continues the discussion on the glee authentication issue #377 , it continues the discussion about glee authentication, from #460 .

Following the idea from @Souvikns to use a separate directory for authentication. Each file in this directory can hold both server and client authentication logic.

/** auth/serverName.ts **/

export function serverAuth({headers, done}) {
  // write logic for authentication 
  done()
}

export function clientAuth() {
  return {
    username: '',
    password: ''
  }
}

Steps to test run authentication

• In the glee root directory, cd examples/anime-http/server,
• The server directory, contains an auth directory that holds a trendingAnimeServer.ts file. The file contains some logic you can edit how you like but it must export the same functions as the code above
• npm run dev to start the server in dev mode
• The same logic applies to the client directory, cd examples/anime-http/server
• Then look for auth/trendingAnime.js update accordingly then start the server.

Related issue(s)
Resolves #377

@Souvikns @KhudaDad414

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
12 Code Smells

No Coverage information
0.6% Duplication