feat: add message endpoint, implement e2e test

[dagmawig]

working on issue #2

Add DATABASE_URL to .env file and run test-e2e script to do the message test.

The test sends a job to a queue with a job name and payload and fetches the job afterwards to confirm the job created.
The job is found in pgboss schema under job table.

[dadiorchen]

This is awesome! The pgboss did exactly what I wanted: use jsonb to store the message, so in this way, in the future, we can query the message by filter easily, this is important to us.

[dadiorchen]

@dagmawig please test the receiving, that is to say, you should subscribe the message queue name: 'add-tree-test' and make sure the message that you sent is received by the client.

like this:

it('test', done => {
  const client = new pgboss.client();
  client.subscribe('add-tree-test', data => {
    expect(data).toMatchObject({message:'ssss'});
    done();
   });
   // do the post

}}

[dagmawig]

In this fix instead of just sending job to queue, it also completes the job and confirms the job completed.

[dagmawig]

@dadiorchen I have replaced pg-boss with postgres listen-notify client system. For the e-2-e test I have created two separate pg clients and confirmed they both receive the notification of record insertion. We can add more functionalities in separate PRs later but I believe this will take care of the need for a proof of concept. Please review and let me know what you think.

[dagmawig]

Below is what the message table looks like. Based on the value under the name column, the queue schema function sends the message to the appropriate channel.