[clang] No warning on dangling iterator of Set containers

[usx95]

All usages are dangling references below:

#include <set>
#include <unordered_set>
#include <vector>

void sets() {
    auto x = std::set<int>{}.find(1);
    auto y = std::set<int>{}.begin();
    auto z = std::set<int>{}.end();
}
void sets2() {
    auto x = std::unordered_set<int>{}.find(1);
    auto y = std::unordered_set<int>{}.begin();
    auto z = std::unordered_set<int>{}.end();
}

void vector() {
    auto y2 = std::vector<int>{}.begin(); // Only warning here. Good!
}

https://godbolt.org/z/Mb4vr31P4

We might be missing [[clang::lifetimebound]] on these methods.

cc: @hokein

[hokein]

This looks like a regression. clang19 is able to diagnose these cases: https://godbolt.org/z/ae1bG7K5T

[hokein]

bisect to 12ccb62, this patch seems to cause some unexpected behavior changes.

[hokein]

Reproduce testcase:

namespace std {
template <typename T>
class __set_iterator {};

template<typename T>
struct BB {
  typedef  __set_iterator<T> iterator;
};

template <typename T>
class set {
public:
  typedef BB<T>::iterator iterator;
  iterator begin() const;
};
}

void sets() {
    auto y = std::set<int>{}.begin();
}