Don't surface form draft warnings or information about `meta/entity` or `meta/entity/label`

[lognaturel]

Now that Entity declaration blocks can be put in groups or repeats, it's possible for two form definitions to have exactly the same Entity effect but have Entity declaration blocks at different levels.

For example, let’s say you start with a form with a top-level Entity declaration. Then you add a new group just to put some fields in a field-list and now all savetos are in that new group. The Entity declaration could be placed in that group instead of at the top level and the effect would be identical.

Currently, when this change is made, Central will highlight that meta/entity and meta/entity/label have changed locations. That's confusing to an end user. Because meta/entity will always be system-generated (by pyxform), Central can filter out any notices related to those nodes.

[srujner]

Is it already on staging and test?
I tried to upload this form from Kathleen issue:

Deeply.Nested.Entities.in.Repeats.label.only.semi-broken.no.savetos.xlsx

and there is no warning in both instances.

[srujner]

Could you give us some more details about what exactly should be tested?
That would be very helpful!

[ktuite]

If you switch between these forms (they have the same xml form ID) you should a warning about fields missing, but that warning should not include anything about meta, entity, or label.

Create trees and cacti.xlsx
Create trees and flowers.xlsx