feat(#128): Store and serve extracted "needs" from message content

[bugthesystem]

Description

Functionality to return needs of locations.

discord username: @bug the system#9283

closes #issue

128

Please describe your changes, the reason for the changes, and the content of the code. Don't forget to list the dependencies that are affected by the change.

Implemented a flow that sends message content to Intent Extractor API to get detailed intent tags (needs) and serve from the backend API.

Prerequisites:

1. The following column needs to be added to the feeds_location table first

   ALTER TABLE public.feeds_location ADD needs JSONB NULL DEFAULT '[]'::jsonb;

2. NEEDS_RESOLVER_API_URL should be set
3. Intent Extractor API has no auth mechanism at the moment, needs to be added, then the NEEDS_RESOLVER_API_KEY env var should be set as well

TODOs

• The type of needs is a string at the moment and needs to be updated to be stored as JSONB.
• Needs Resolver API has no auth mechanism at the moment, needs to be added
• GetLocations and GetFeed methods need to be updated to query the needs JSONB field instead of the string

Things to do before you open the PR

• [x] I inspected and reviewed my own code.
• [ ] If it's a core feature, I've run detailed tests.

Rules for opening PRs

• [ ] You must open a PR for an already existing issue. Otherwise, the PR will be rejected.
• [ ] Relevant issue number: Add the issue number in the '#issue' field below the discord username.
• [ ] Clear and concise title: The PR title must be representative of the purposes and qualities of the actual code changes. It must be at the top of the comment. It must follow the semantic commit rules. For example: "docs(#issueId): Add README.md".
• [ ] Relevant document choice: Only the relevant files must be changed and other files should remain untouched.
• [ ] Formatting and Linting: Code must have been passed through the linters used by this repository.
• [ ] Clean commit history: Commits with the changes need to be well-ordered and descriptive.
• [ ] Completed: PR should only be opened after the work is done, and must be sent to the other team members for review.

Changes

• [x] New Feature (Non-breaking)
• [ ] New Refactor (Non-breaking performance or readability-based changes)
• [ ] Breaking change
• [ ] Updated Docs

How were these changes tested?

Please explain the actions you've taken to test these changes. Please also explain your testing environment.

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

[bugthesystem]

JSONB Notes on working with Array content

Schema (PostgreSQL v14)

CREATE TABLE test (
  id INT,
  payload  jsonb null default '{}'::jsonb
);
INSERT INTO test (id) VALUES (1);
INSERT INTO test (id) VALUES (2);

ALTER TABLE test ADD needs JSONB NULL DEFAULT '[]'::jsonb;

INSERT INTO test (id, payload, needs) 
            VALUES (3, '{}', '[]');
INSERT INTO test (id, payload, needs) 
            VALUES (4, '{}', '[{"status":true, "label": "mama"}, {"status":false, "label": "mont"}]');

---

Query #1

Use jsonb_array_elements() to unnest the jsonb array and the aggregate function jsonb_agg() to get the result in a single row:

SELECT id, jsonb_agg(elem->'label') as active_needs 
    FROM test 
    cross join jsonb_array_elements(needs) as elem
    where (elem->>'status')::boolean = true
    group by id;

id	active_needs
4	mama

---

[bugthesystem]

Closed, superseded by https://github.com/acikkaynak/deprem-yardim-backend-go/pull/132