chore: add plugin hostname to plugin configuration

[cmeessen]

Fixes connection issues when running nextjs in a docker container.

Changes proposed in this pull request:

• changes the plugin settings in frontend/public/data/settings.json to also include the hostname of the plugin backend, which is required to make the requests inside the docker network

How to test:

• change plugins array in settings.json to:

  "plugins": [
    {
      "name": "dummyplugin",
      "backend_hostname": "dummy-plugin-backend:8081"
    }
  ]

• build and run the application and verify that backend is reached by next

@dmijatovic please review this solution. I will update the documentation after you will have accepted.

PR Checklist:

• [ ] Increase version numbers in docker-compose.yml
• [ ] Link to a GitHub issue
• [ ] Update documentation
• [ ] Tests

[sonarcloud[bot]]

Quality Gate passed for 'rsd-frontend'

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[dmijatovic]

@cmeessen I tested your proposal with the plugin example I was working on and came to conclusion that I favor direct link to the config endpoint of the plugin. This approach supports various scenarios like: api versioning and running frontend in dev mode. It does require config_url to be changed in various scenarios but it does not impact core RSD code. I have pushed additional commit with the preferred approach.

In addition, I removed useMemo advised by SonarCloud because it does not adds the value. The suggested approach is not correct as far as my knowledge goes. So please ignore SonarCloud issue.