fix(ingest/tableau): project_path_pattern use in _is_denied_project

[sid-acryl]

No description provided.

[hsheth2]

overall this code still confuses me

why do we have both is_allowed_project and is_denied_project? why isn't one method sufficient here? also, ideally we'd just use AllowDenyPattern's built-in methods instead of re-implementing a bunch of regex matching logic here

[sid-acryl]

overall this code still confuses me

why do we have both is_allowed_project and is_denied_project? why isn't one method sufficient here? also, ideally we'd just use AllowDenyPattern's built-in methods instead of re-implementing a bunch of regex matching logic here

@hsheth2
It took me while to recall why I did it like this. I added a below doc string in the function _is_denied_project and also renamed the AllowDenyPattern._denied to AllowDenyPattern.denied to reuse the regx logic.

    """
    Why use an explicit denial check instead of the `AllowDenyPattern.allowed` method?

    Consider a scenario where a Tableau site contains four projects: A, B, C, and D, with the following hierarchical relationship:

    - **A**
      - **B** (Child of A)
      - **C** (Child of A)
    - **D**

    In this setup:

    - `project_pattern` is configured with `allow: ["A"]` and `deny: ["B"]`.
    - `extract_project_hierarchy` is set to `True`.

    The goal is to extract assets from project A and its children while explicitly denying the child project B.

    If we rely solely on the `project_pattern.allowed()` method, project C's assets will not be ingested.
    This happens because project C is not explicitly included in the `allow` list, nor is it part of the `deny` list.
    However, since `extract_project_hierarchy` is enabled, project C should ideally be included in the ingestion process unless explicitly denied.

    To address this, the function explicitly checks the deny regex to ensure that project C’s assets are ingested if it is not specifically denied in the deny list. This approach ensures that the hierarchy is respected while adhering to the configured allow/deny rules.
    """

I will create a separate PR to add test cases for this scenario.

[hsheth2]

@sid-acryl let's create some unit tests for that scenario

[sid-acryl]

@sid-acryl let's create some unit tests for that scenario

@hsheth2
Added test-case here #12079