[NFC] Explicitly set dialects to usePropertiesForAttributes=0 in preparation for https://reviews.llvm.org/D158581 (flipping the default to 1) to land.

[copybara-service]

[NFC] Explicitly set dialects to usePropertiesForAttributes=0 in preparation for https://reviews.llvm.org/D158581 (flipping the default to 1) to land.

This allows us to switch dialects to use properties one by one.

[AlexanderViand-Intel]

Since this came up in #123

Also see the very timely PR #124 which seems to opt us out of a migration to use properties as the default. If you're interested in digging into how to use properties instead of attributes, feel free to flip that flag back after it lands.

From my understanding "inherent attributes" (i.e., attributes that are part of the OP's definition and not something tagged on as part of an analysis/transformation) should really switch over to properties (for various reasons described in the properties RFC) so imho we should either not merge this, or merge this but then flip the flag back as soon as we can.

EDIT: I'm actually somewhat confused by what's going on with this PR, the copybara bot seems to be going a bit mad here?

[asraa]

or merge this but then flip the flag back as soon as we can.

I think so too. I'm a little fuzzy still on the cases for when not to use a property, so I might need some help understanding the tradeoffs from the RFC. I can file an issue to flip the flag back and perform some op attribute migrations.

the copybara bot seems to be going a bit mad here?

It's really weird but copybara bot, after a PR is approved (by one of us internally), closes the PR and merges the commit to the main branch directly (9ec8628)