Do not lint assertions_on_constants for const _: () = assert!(expr)

[StackOverflowExcept1on]

Fixes #8159

pub fn f() {
    // warning
    assert!(true);
    assert!(usize::BITS >= 32);

    // ok
    const _: () = assert!(usize::BITS >= 32);
}

changelog: Fix const _: () = assert!(expr) false positive on assertions_on_constants lint

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Jarcho (or someone else) soon.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[Jarcho]

Thank you. @bors r+

[bors]

📌 Commit 90ece56 has been approved by Jarcho

It is now in the queue for this repository.

[bors]

⌛ Testing commit 90ece56 with merge dd857f8...

[bors]

☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test
Approved by: Jarcho
Pushing dd857f8 to master...

[CAD97]

This fixed the simple case of const $ident: $type = assert!(...);, but doesn't handle any nesting (e.g. = { assert!(...); };) yet. repro in issue