Implement search in namespace context

Implemented search in custom namespaces with x-collaboration header. The code is feature flagged with collaborations-enabled flag

curl --location 'localhost:8092/api/search/v2/query' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: osdu' \
--header 'x-collaboration: id=96d5550e-2b5e-4b84-825c-646339ee5fc7,application=pws' \
--header 'Authorization: ••••••' \
--data '{
	"kind":"osdu:search1717500302132:test-data--Integration:1.0.6"
}

When we send request with x-collaboration will be add part to request to ElasticSearch:

        "bool": {
            "must": [{
                "bool": {
                    "must": [{
                        "bool": {
                            "must": [{
                                "exists": {
                                    "field": "x-collaboration"
                                }
                            },{
                                "term": {
                                    "x-collaboration": "id=96d5550e-2b5e-4b84-825c-646339ee5fc7,application=pws"
                                }
                            }]
                        }
                    }]
                }
            }]
        }

If we will send request without x-collaboration header:

curl --location 'localhost:8092/api/search/v2/query' \
--header 'Content-Type: application/json' \
--header 'data-partition-id: osdu' \
--header 'Authorization: ••••••' \
--data '{
	"kind": "osdu:wks:master-data--CollaborationProject:1.0.0",
    "query": "id:\"osdu:master-data--CollaborationProject:275f1abfc7c44f35b5173e7c987638e8\""
}

To request will be added:

    "bool": {
      "must_not": {
        "exists": {
          "field": "x-collaboration"
        }
      }
    }

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [YES]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• Google Cloud
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

We can't searching in different custom namespaces

What is the new/expected behavior?

We can searching in different custom namespaces

Have you added/updated Unit Tests and Integration Tests?

Added Unit and Integration tests

Any other useful information

Link to task

Link to ADR

Before merging this MR we should merge MRs with constants before, according to comment !653 (comment 316947)

assigned to @Pavel_Barzou

added 1 commit

• 4f110136 - #89 (closed) Fix unit tests

Compare with previous version

added 2 commits

• b92e8ac2 - Working with int tests
• d3499c07 - Temporary changes for local running with 47lining

Compare with previous version

changed title from #89 inplement search in namespace context to Implement search in namespace context

changed the description

added AWS label

requested review from @Rostislav_Dublin

added 2 commits

• 79283082 - Revert "Temporary changes for local running with 47lining"
• 66263d37 - Add Integration tests with documentation

Compare with previous version

added 1 commit

• 874c9772 - Fix feature flag

Compare with previous version

added 1 commit

• 4a685e8a - Fix feature files

Compare with previous version

added 1 commit

• 27b22895 - Add default tag to all tests

Compare with previous version

changed the description

added 1 commit

• 6a839f0f - Fix extra changes

Compare with previous version

added 1 commit

• bb5fee8d - Updating NOTICE

Compare with previous version

added 1 commit

• 835fc19a - Add constants to test

Compare with previous version

added Common Code label

changed milestone to %M24 - Release 0.27

added P&WS label

resolved all threads

added MRNew Feature label

the description query have nested

"query": {
        "bool": {

why is that for? one bool should be enough.

changed the description

resolved all threads

@Pavel_Barzou , can you please rebase and resolve conflicts.

added 5 commits

• 835fc19a...8d1c2ebd - 4 commits from branch master
• 142bc3dd - Merge branch 'master' into #89 (closed)-inplement-search-in-namespace-context

Compare with previous version

resolved all threads

approved this merge request

approved this merge request

added 1 commit

• 1066cc8c - Fix property name

Compare with previous version

reset approvals from @thulasi_dass and @solxget by pushing to the branch

added 1 commit

• b32ea5c1 - Added support for a new version of the core-common

Compare with previous version

added 1 commit

• c444a202 - Updating NOTICE

Compare with previous version

mentioned in merge request !664 (closed)

mentioned in merge request osdu/platform/deployment-and-operations/terraform-deployment-aws!48 (closed)

approved this merge request

approved this merge request

Can you please rebase your MR, it's behind 8 commits?

I see all collaboration-enabled is set to false for all providers, then how are we validating this change via integration tests? Are they even running?

changed the description

mentioned in merge request osdu/platform/system/lib/core/os-core-common-spring6!7 (merged)

mentioned in merge request osdu/platform/system/lib/core/os-core-common!273 (merged)

added 10 commits

• c444a202...a72a9538 - 8 commits from branch master
• 1c8e15ae - Improve request to elastic, integration tests
• c392f26d - Merge branch 'master' into #89 (closed)-inplement-search-in-namespace-context

Compare with previous version