htmlLocalCopySwitch functionality needs to be "fixed"

[UmakanthOS]

The idea behind htmlLocalCopySwitch is that setting the switch to true results in a full copy of the filestructure / files from the network share being duplicated on the VMSS node/instance local disk. There's a bug with how this works in the current LAMP template.

The bug is that the wp-content directory under /var/www/html on the VMSS node is still pointing to the network share (under /azlamp) and not a true local copy. This means that any content being served from the VMSS node will result in accesses to the network share resulting in poor performance. If htmlLocalCopySwitch is set to true, the VMSS local copies need to be true local copies.

Repro steps:

1. Deploy a LAMP deployment: I used CMS:WordPress to true, used a D16s_v4 as the VMSS size despite choosing the Large deployment option
2. SSH into VMSS instance after infrastructure creation and check the directory structure under /var/www/html/. Specifically check where wp-content points to.

[UmakanthOS]

Flagging with @ummadisudhakar and @naioja

[UmakanthOS]

Please also note that the issue here is WP specific but the idea is that htmlLocalCopySwitch should "just work" and no symbolic links to the network file system should manifest themselves under the VMSS /var/www/html structure :)