[BUG] Attempts at view composition can produce awful errors

Describe the bug

View composition can lead to unintelligible error, as per screen capture. Tactical fix is disallow views citing views at creation time.

To Reproduce

create view cross_cloud_disks1 as select 'google' as vendor, name, split_part(split_part(type, '/', 11), '-', 2) as type, sizeGb from google.compute.disks where project = 'stackql-demo' and zone = 'australia-southeast1-a' union select 'aws' as vendor, volumeId as name, volumeType as type, size as SizeGb from aws.ec2.volumes where region = 'ap-southeast-2' ;

-- simple view composition (surprisingly) does work
create view zz as select * from cross_cloud_disks1;

select * from zz;

-- less suprisingly, complex view composition does NOT work
create view zz1 as select * from cross_cloud_disks1 d1 inner join cross_cloud_disks1 d2 on d1.name = d2.name ;

select * from zz1;

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

Non sono indicati file o test. Inizia riproducendo gli esempi SQL per la composizione di viste semplici e con join, quindi segui il percorso di creazione delle viste e la relativa gestione degli errori. Il lavoro è completato quando la composizione di viste viene rifiutata al momento della creazione con un errore chiaro e i casi mostrati sono coperti.