ContainerLogsV2 and Basic Logs support

[samaea]

PR Summary

Addresses issue #437.

In addition, added:-

• updateDependencyFn() function (under addonsTabs) that assists with enforcing dependency between two features (e.g. In order to activate Basic Logs on Container Logs V2, you also need to enable the Container Logs V2 schema. It might be worth considering to make this a global function instead (i.e same place as where updateFn() is defined).
• Under deployTabs, preview_post_params array has been added to support flagging preview features passed as params to the postdeploy script. At present, we are only capturing preview params under ARM/Bicep.

PR Checklist

• PR has a meaningful title
• Summarized changes
• This PR is ready to merge and is not Work in Progress
• Link to a filed issue
• Screenshot of UI changes (if PR includes UI changes)

[samaea]

👋 @khowling, incorporated feedback from our PR discussion. Also added another function in addons.js to ensure any features dependent on the ContainerLogsV2 schema are disabled as well (at present it only accommodates for the Basic Logs feature). This avoids the scenario where the user selects on Basic Logs (which automatically selects the ContainerLogsV2 feature) and then decides to disable the ContainerLogsV2 feature (i.e safety guard in both directions now).

[khowling]

hey @samaea , looking good! I just tested the UI, and one small thing, in Monitoring, If I select 'Azure Monitor for Containers', then select the V2 Logs, the parameters appear on the deployment command as expected. But it I then select 'None' for Monitoring, the V2 log parameters still appear. To fix this, can you add an additional check in the deployment logic, take a look at this as an example

[samaea]

hey @samaea , looking good! I just tested the UI, and one small thing, in Monitoring, If I select 'Azure Monitor for Containers', then select the V2 Logs, the parameters appear on the deployment command as expected. But it I then select 'None' for Monitoring, the V2 log parameters still appear. To fix this, can you add an additional check in the deployment logic, take a look at this as an example

Hey @khowling - great catch! All done. :)