... as required by ECMAScript.

Pick-to: 6.7 6.5
Change-Id: I31bc7e6a87e404a8e6d314c99f163f82208e13a1
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

By using an "as" cast you want to check the type of the value, not
coerce it. Previously, however, if you did this with a value type, it
would create the value type instead of just checking for it.

Add an attribute "Assertable" to the ValueTypeBehavior pragma that
prevents this and enables the correct behavior. Also print a warning
when coercing as part of an as-cast.

[ChangeLog][QtQml] A new attribute "Assertable" has been added to the
"ValueTypeBehavior" pragma. You should always use it if you want to
type-check value types using "as". If you don't use it, an instance of
the type is created as result of the "as" if the type doesn't match.

Task-number: QTBUG-124662
Change-Id: I1d5a6ca0a6f97d7d48440330bed1f9f6472198aa
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

This way you can create them using new and populate them manually
(provided you have a way of obtaining type references to them).

Task-number: QTBUG-124662
Change-Id: Icceacaefafc311044d519e4af011b078dbf2f1e7
Reviewed-by: Olivier De Cannière <olivier.decanniere@qt.io>
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

This calls any invokable ctors and only invokable ctors. Any
type that doesn't have an invokable ctor won't even expose a
function, since functions are determined by the presence of call
methods.

QMetaObjectWrapper gains the same functionality since the code is
shared. It can now not only create object types but also value types.

Task-number: QTBUG-124662
Change-Id: Ib30098666f67aef7a1f464f52d9b0bbd70d896d1
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>

Also, replace the import in the example to the minimal required one, so
it doesn't imply like if you need the whole QtQuick to create a
component from "QtQuick" URI. It could be confusing to the readers.

Amends 6656567a4085e3d6de01226fb7b1ec16ee7ba08c

Change-Id: Ibb79c83ea781e3820f505322266d38b325e4c8b2
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

Calling `qmllint` can produce warning for usages of the `QJsonArray`
type, due to it not being found.

Nonetheless, the engine special handles the type, so that `qmllint`
should not warn about it.

Make `QJsonArray` a builtin type so that calls to `qmllint` will import
and recognize the type.

Add a test-case to ensure that the type is now recognized.

Task-number: QTBUG-111015
Change-Id: I51744968a0316ccb016a4404326b74fa419037bd
Reviewed-by: Sami Shalayel <sami.shalayel@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

When a property coming from C++ is used in a QML file, the engine might
perform some internal conversion to handle the type.

When a `QJsonArray` property is loaded, currently, it will be converted
to an internal `JsonObject` representation containing an engine-owned
array.

When the conversion is done, the data from the `QJsonArray` is copied as
a part of this process.

The performed copy is expected to act like a Javascript array.
Nonetheless, due to the way the conversion is implemented, using the
property will perform the requested work on the copy without writing
back to the original property.

This in turn prevents certain operation from working as expected, in
particular the mutable methods on the array prototype.

For example, if `jsonArray` is a `QJsonArray` property with a C++
provenance, the following will not register the push on the original
property, so that it will be lost the following time the property is
accessed:

```
...
jsonArray.push(4)
...
```

As a `QJsonArray` property should behave as a Javascript array when used
from QML, a `QJsonArray` property will now be converted to a `Sequence`,
an internal representation that behaves like a Javascript array but acts as a
reference object with property write-backs, to allow in-place mutations
to be correctly reflected on the original property.

Currently, a `QJsonArray` `Sequence` call to the sort method will not
correctly work due to the way the sort method is implemented.
This is currently left as non-working and will be fixed separately.

A non-exhaustive test-case was added to check that a C++ loaded
`QJsonProperty` acts as a Javascript array with regards to the Array
prototype methods, taking into consideration the inability of the sort
method to currently work.

Task-number: QTBUG-111015
Change-Id: Iec48fe4cba9adb9b794e5a568985b86b8da4556c
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

androiddeployqt needs the path to qmldom tool to invoke it to
extract QML dom information. The output later will be used to
generate QQmlComponent subclasses that has component information
such as library name, module name, and QML qrc path.

ADQt will also use property & method information extracted using
qmldom, to add typed property getters/setters, as well as typed
signal connection methods.

Task-number: QTBUG-124846
Change-Id: I7f3fb4e6afab92d114154139d34664f1629ecd29
Reviewed-by:  Alexey Edelev <alexey.edelev@qt.io>
Reviewed-by: Assam Boudjelthia <assam.boudjelthia@qt.io>

Add the wrapping struct that registeres the QML_FOREIGN QByteArrayList
container in QML.

The type could be useless in QML context, but Qt submodules generate
the scriptable properties of this type, so it's expected that the type
is registered by QML builtins.

Task-number: QTBUG-125240
Change-Id: I47bf224ba3b5bf23911c02c451f49f2a1148c75f
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

-Wswitch-enum is a stricter version of -Wswitch, kicking in even in
the presence of a default: case label. We intend to add -Wswitch-enum
to headersclean, so fix the warnings here by listing all enumerators
explicitly.

Pick-to: 6.7
Change-Id: Ib015b27dc9186f49a941528425eb14e8f5bec987
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>