CORE-558 Refactor and Optimize Signal Loader Logic

[ogiste]

What does this PR do?

• Refactor load signals logic -- Render all signals from Signal context --- Load all datatoken addresses into the Signal context --- Load urls in Signal context --- Pass urls and load signals within signal context not AssetsList component --- Add timeout for signals (4000ms) --- Add loading signals indicator -- Update text on settings page when creating new custom signals

Description of Tasks to be completed?

As a user, I want to see UTU signals for on the ocean assets when I visit the ocean market and have them render quickly without preventing me from seeing the asset cards

How should this be manually tested?

In the project directory, you can run:

$ npm install

$ npm start

Any background context you want to provide?

None

What are the relevant Jira Stories?

#CORE-558

Screenshots

[sonarcloud[bot]]

SonarCloud Quality Gate failed.   

1 Bug
0 Vulnerabilities
0 Security Hotspots
13 Code Smells

No Coverage information
0.0% Duplication