Use common config file

Changes

• Create a config file for the UL CL scenario
• Create a config file for basic NRF scenario
• Create a config file for basic VPP NRF scenario (only needed temporary)
• Create a config file for mini NRF scenario
• Create a config file for mini non-NRF scenario
• Use these config files for the PCF (see oai-cn5g-pcf!26 (merged))
• Use these config files for the SMF (see oai-cn5g-smf!202 (merged))
• Use these config files for the NSSF (see oai-cn5g-nssf!31 (merged))
• Use these config files for the NRF (see oai-cn5g-nrf!45 (merged))
• Requires UDM fix (see oai-cn5g-udm!42 (merged))
• Requires AMF fix (see oai-cn5g-amf!220 (merged))

Tests

@defosseu @arora I tested manually with all the docker-compose files, as well as the tutorials we run in the CI.

The DNS resolving and PFCP Node ID Mapping is a bit different in SMF, which is why we need the extra host for the non NRF spgwu scenario.

I tested:

• HTTP/1 and HTTP/2 for all NFs
• Use local subscription yes/no on SMF (e.g. static IP tutorial)
• UL CL with verifying that the routes / PCC rules are set correctly

Disclaimer

I tried to put all the variables for the other NFs as well in the config file, but because it is not implemented there, it may be subject to change.