One test. Two setup steps.
What you have described is very common, particularly as test scenarios get more complex.
What you need is one test with setup that does the user logging in, the user selecting the item (save the id) and then deleted and then you go the dashboard.
So don't think in terms of your two existing tests, think in terms of a new test but with more setup steps.
This is frequently a case of 'sounds easy, but in practice...' and you will frequently run into issues about
- authentication as different users and switching between them
- storing authentication details
- items ID's being dynamic and changing with each run
These can be difficult issues often involving organizational security and access issues. It's best to have a detailed discussion with the relevant folks in your organization so everyone understand the problem and is on-board with the solution. Be sure to involve application developers so their knowledge and skills help and also so that they are fully on-board with it and feel shared ownership. Include security folks as necessary or compliance folks may stop by to say hi.
In trying to achieve this you may indeed run into issues with 'organizational policy'. This is why you need the conversations. You need policy and implementations that achieve the business goals securely. In my experience, many organizations over 5-10 years old struggle with this, much more technical approach to QA and the engineering approaches and needs that it involves.
Longer term, having tests needing to use real authentication will be increasingly problemsome and this dependency needs to be removed. When there is an actual problem with authorization you want one, or at most a few, authorization tests to fail. The rests of the tests should be able to run with a mocked out authentication process, or at the very least, not run at all. Smoke tests can be very helpful here, for example testing that deployments havent broken authorization processes. Otherwise you will have hundreds or thounsands of tests failures when there is a problem with authorization.