[Bug] Fix bug that The MetaObject lock design of fe would cause some problems with consistent meta when catalog do replay operation

[caiconghui]

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)
• Code refactor (Modify the code structure, format the code, etc...)
• Optimization. Including functional usability improvements and performance improvements.
• Dependency. Such as changes related to third-party components.
• Other.

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have created an issue on (Fix [Bug] The MetaObject lock design of fe would cause some problems with consistent meta when catalog do replay operation #6649 ) and described the bug/feature there in detail
• Compiling and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• If these changes need document changes, I have updated the document
• Any dependent changes have been merged

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[caiconghui]

here, we only need to check state of meta object when get write lock except the following conditions,

1. replay operation
2. already get parent meta object lock

[caiconghui]

1. If the table or db has been dropped，we will get write lock failed or just skip or throw exception，
2. and if we recover table or db， we must ensure that unmark dropped state after writing recover journal.
3. db.dropTable corresponds to db.createTable, I don't move table.markDropped method to the db.dropTable, for that all meta added to db or catalog must after writing recover journal, so we must invoke markDropped and unmarkDropped method outside the dropTable and createTable method.

[morningman]

How about moving markDropped() inside the db.dropTable() and catalog.onEraseOlapTable() method?
So that we don't need to call markDropped() every time along with these methods manually.

And also, add markUndropped() method to db.createTable() method to address the operation like modifyView or renameTable, etc.

[morningman]

LGTM

[github-actions]

PR approved by at least one committer and no changes requested.

[github-actions]

PR approved by anyone and no changes requested.