bluetooth: mesh: Mark BT_MESH_USES_TINYCRYPT as deprecated

[PavelVPV]

Since TinyCrypt is deprecated, we need to mark BT_MESH_USES_TINYCRYPT option as deprecated too so it is visible for the customers that they need to switch to MbedTLS.

[jhedberg]

@PavelVPV you also need to remove all places that might set this option in the upstream tree (when deprecating something the policy is to not have anything in the upstream tree use it anymore, in particular because CI doesn't accept such configurations and would result in CI failures)

[jhedberg]

I did a quick grep, and it seems there are still users of this in the upstream tree.

[PavelVPV]

@PavelVPV you also need to remove all places that might set this option in the upstream tree (when deprecating something the policy is to not have anything in the upstream tree use it anymore, in particular because CI doesn't accept such configurations and would result in CI failures)

This would duplicate the work has been done and not finished in #79931 which makes no sence, but I wonder how then TinyCrypt deprecation got merged without changing its users as this rule should have also been applied there?

[jhedberg]

This would duplicate the work has been done and not finished in #79931 which makes no sence, but I wonder how then TinyCrypt deprecation got merged without changing its users as this rule should have also been applied there?

Let's continue the discussion in #release on Discord. I'm not trying to come up with my own rules here but just stating what my understanding of the policy is. I think it's better to have a clear answer before merging anything like this, so that you don't end up with last-minute forced reverts before the final 4.0 release.

[jhedberg]

@PavelVPV I didn't realize that #79566 was already merged and that sets the Kconfig option as deprecated. It's possible it'll have to be reverted (let's see what the consensus of the release engineering team is).