Render the start marker, placeholder and end marker for list areas even if the area does not have any availableComponents defined yet. Today, the system treats such an area as empty and non-editable, and does not render it on the page. This is a problem for users who build their templates in the following typical order:

1. Create a page script and a page definition. Assign to a page. See what the page looks like in the browser.
2. Create an area script and an area definition. Reload the page. Nothing is displayed! Where's my area?
3. Create a component script and a component definition. Make the component available in the area. Reload the page. Now the empty area is rendered.
   
   

The problem comes in step 2. If the area is of type list, it is not rendered on the page because no available components are defined. We cannot expect the user to define components before the area.

To resolve this, make an exception that renders a list area even if it doesn't have available components defined yet.