Fix Admin UI configuration and navigation

[magdasmat]

Summary

This PR updates the Admin UI to work with the current Beacon configuration structure and makes it accessible from the Template UI.

Changes

• adminui/adminbackend/forms/entry_types.py

  • Loads entry type settings from the current YAML configuration files.
  • Initializes form fields using the configured entry type status, endpoint, granularity, query and lookup settings.
  • Allows endpoint-related fields to remain optional when an entry type is disabled.

• adminui/adminclient/views/views.py

  • Reads and updates Entry Types configuration directly in the corresponding YAML files.
  • Preserves the existing per-entry-type update blocks while replacing access to the obsolete Python configuration files.

• adminui/adminclient/views/datasets.py

  • Uses the MongoDB datasetsConf collection as the source of truth for dataset configuration.
  • Reads and updates the isTest and isSynthetic dataset attributes through the Admin UI.
  • Removes the associated dataset configuration when a dataset is deleted.

• adminui/templates/general_configuration/datasets.html

  • Separates the global test mode form from individual dataset forms.
  • Associates Save and Delete actions with the correct forms.

• adminui/templates/home.html

  • Adds navigation links to be available from Admin UI.

• template-ui/src/config/config.json

  • Adds access to the Admin UI from the Template UI (login is required).

Purpose

The purpose of these changes is to allow Beacon configuration to be managed correctly and remotely through the Admin UI using the current YAML-based entry type configuration, MongoDB-based dataset permissions and configuration, fix navigation issues, and expose the Admin UI through the Template UI.