After talking to support it turns out there is a "bug" that lies somewhere between the Dell extended schema and Server 2019/2022 domain controllers.  My troubleshooting with the schema in my first post was correct, the new objects are being tagged in a way that the Association object cannot find them.  The fix was to manually set a property on the newly created objects so the associating object can find them.  However for me that DID NOT WORK at first.  After doing tech supports fix I was able to find the devices but I still could not login.  So I ended up wiping everything out and recreating which did work.  Here is the step by step It is now working for both my old iDRAC8's and the new idRAC9.  
Have followed all the "Integrating DRAC into AD" posts and had everything working correctly with two iDrac 8 devices in R630's.  Went to add a new iDrac 9 in a R650, set everything on the card up.  Went into Active Directory and created a new "Dell remote Management Object Advanced" with a type "iDrac Device Object".  Open up the properties of the association object so I can add it in there but it can't find it.  Try a couple more times, still can't find it.  Sees the old DRAC objects just fine.  So I delete and recreate the association object.  Same thing, sees the old objects but not the new one.   At this point I open up the Dell Remote Access Configuration Tool.  Add in the two old DRAC cards and the one new one.  Verify the password.  Verification fails only on the new one, works on the two old ones.  Log out of the DRAC and back in with the same information without issue so it's not the user/password.  Saw some posts saying the DRAC doesn't like punctuation, which doesn't make sense since the old ones are fine, but I create a new user with a simple password.  Still fails verification.  At this point I figure maybe the Dell RACT hasn't been updated for the new iDrac9 so I move on. (Is this a bug?)   I have upgraded all my domain controllers to Server 2019 in the last year so I figure maybe the schema needs to be updated.  I download the latest DRAC schema from the OMSA disk and reran the extend from the PDC logged in as the domain admin.  Every line said "failed" with a reason being "property already exists" so that wasn't it.    Finally I create a dummy iDRAC and try adding that.  Not found but again the old objects are.  So no "new" object I create can be found.  As a last ditch try I open up ADSIEdit to see if there was a different between the "old" object that work and the "new" objects I'm trying to add and sure enough there was:   Old Dell Remote Management Device (Working) primaryGroupID:  513 = (GROUP_RID_USERS) sAMAccountType:  805306368 = ( NORMAL_USER_ACCOUNT )   New Dell Remote Management Device (Not Working) primaryGroupID:  515 = (GROUP_RID_COMPUTERS) sAMAccountType:  805306369 = ( MACHINE_ACCOUNT )   The Association Object is searching for "Users" so this makes perfect sense why I can't add the new ones.  Problem is if I try to change the properties I get a security error.  So the real question is why is AD creating the new Dell objects as a "computer" and not a "user".  Second question is how do I fix this?
Cannot get Dell Remote Management Device object added to Association Object