Adding NL Places Search UI & Functionality

[TheRBajaj]

• includes toggle to activate nl places search
• NL search UI will only be present if correct env variables are set
• added appropriate cypress and jest tests for all NL Search related components code refactor

Screenshots

Cypress

• Cypress test for userIsableToSearch is intended to fail as workflow tests cypress with different web domain

working test with local web domain:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[its-aazizi]

1. The textual content has only been added to en.json. It needs to be added to update-en.json and then translated using the translation script under /extra folder. The content also needs to be added to marketing repo, because when the build is created the demo lib uses locales from the marketing repo.
2. I see that 2 new ENV variables have been introduced. Shouldn't the default CF template also be updated to create those resources under /extra/cloudformation/default-unauth-resources-template.yaml?
3. .env and .env.example also needs to be updated in the marketing repo. Since during build, demo lib will be created using the env from the marketing repo.

Let me know if anything is unclear, and I'll be more than happy to hop on a call and clarify.

CC: @vinguthh @TheRBajaj

[TheRBajaj]

1. The textual content has only been added to en.json. It needs to be added to update-en.json and then translated using the translation script under /extra folder. The content also needs to be added to marketing repo, because when the build is created the demo lib uses locales from the marketing repo.
2. I see that 2 new ENV variables have been introduced. Shouldn't the default CF template also be updated to create those resources under /extra/cloudformation/default-unauth-resources-template.yaml?
3. .env and .env.example also needs to be updated in the marketing repo. Since during build, demo lib will be created using the env from the marketing repo.

Let me know if anything is unclear, and I'll be more than happy to hop on a call and clarify.

CC: @vinguthh @TheRBajaj

1. Issue has been resolved. added textual data using translation script for demo-web. Also updated it for merketing demo (PR to follow)
2. these two new env variables are optional for now since this feature will only go to pre-prod for now
3. updated .env.example to reflect the new optional env variables (PR to follow on marketing repo)