Add GitHub Actions workflow and fix failing tests

[dhruvan2006]

• Added a new pytest.yml workflow. I believe this will help to prevent situations like Support custom period in Ticker.history() #2192 Fix: custom period PR breaking Ticker.history() #2211
• Removed checking of keys in Analyst tests because of removal of hardcoded keys Fix: Remove hardcoded keys in Analysis #2194
• Fixed a bunch of tests (Had lot of flakiness with caching in session_gbl)

FAILED tests/test_price_repair.py::TestPriceRepair::test_repair_bad_div_adjusts - KeyError: 'currency'
FAILED tests/test_price_repair.py::TestPriceRepair::test_repair_bad_stock_splits - KeyError: 'currentTradingPeriod'
FAILED tests/test_price_repair.py::TestPriceRepair::test_repair_zeroes_daily - AssertionError: np.False_ is not true
FAILED tests/test_prices.py::TestPriceHistory::test_duplicatingWeekly - IndexError: index -2 is out of bounds for axis 0 with size 1
FAILED tests/test_prices.py::TestPriceHistory::test_prune_post_intraday_asx - AttributeError: 'Index' object has no attribute 'date'
FAILED tests/test_prices.py::TestPriceHistory::test_prune_post_intraday_us - AttributeError: 'Index' object has no attribute 'date'
FAILED tests/test_ticker.py::TestTickerEarnings::test_earnings_dates_with_limit - AssertionError: 109 != 110 : Wrong number or rows
FAILED tests/test_ticker.py::TestTickerAnalysts::test_growth_estimates - AssertionError: Element counts were not equal:

@ValueRaider Can you verify the change made to SCR.TO repair test?

[ValueRaider]

Can you comment-out the CachedLimiterSession stuff not delete it? It's useful when debugging failing tests that fetch live data.

[dhruvan2006]

Can you comment-out the CachedLimiterSession stuff not delete it? It's useful when debugging failing tests that fetch live data.

Yes

[ValueRaider]

Claude suggested some improvements to action, I'll let you review:

name: Pytest

on:
  pull_request:
    branches: [ master, main, dev ]

jobs:
  test:
    runs-on: ubuntu-latest
    
    steps:
    - uses: actions/checkout@v3

    - uses: actions/setup-python@v4
      with:
        python-version: "3.10"
        cache: 'pip'
        
    - name: Install dependencies
      run: |
        python -m pip install --upgrade pip
        pip install -r requirements.txt pytest

    - name: Run non-cache tests
      run: pytest tests/ --ignore tests/test_cache.py -v --junitxml=test-results.xml

    - name: Run cache tests
      run: |
        pytest tests/test_cache.py::TestCache
        pytest tests/test_cache.py::TestCacheNoPermission

    - name: Upload test results
      uses: actions/upload-artifact@v3
      if: always()
      with:
        name: test-results
        path: test-results.xml

[dhruvan2006]

Excluded test_price_repair.py

I think it would be better to upload test-results on push to main/dev if you want to display them as a badge on README for example, rather than uploading them on the pull_requests